Skip to main content
Windward

Product End of Life

 

Overview

This page details the past versions of Windward we support, and to what extent we support them.  Please remember that our first recommendation is always to upgrade to the newest version.  If you are current on support and using the latest version, you don't need to worry about any of this--this page is only relevant if you are using an older version of Windward.  If you have any questions, please don't hesitate to contact us.

Support

  • End of life dates are listed below for all versions except the current version. Our guidelines for the dates set are, based on the release date of the subsequent version:
    • Formatting & Layout bugs are handled for 6 months subsequent.
    • Exception & Failure bugs are handled for 18 months subsequent.
    • Security Issues (we've never had one) are handled for 5 years subsequent.
    • (See the Definitions section below for what these terms mean.)
  • For issues in an older version, we strongly recommend upgrading to the latest version. Version changes are generally not a significant change in existing functionality but more of a calendar event so an upgrade from version 11.1.37 to 11.1.38 is not much different from an upgrade from 11.1.38 to 12.0.0. You get new features but the existing features are unchanged. (The upgrade from version 9 to version 10 is an exception - that has significant changes in how selects are specified.)
  • If you have a current support contract and are using a no longer supported version, you can still submit support requests to our helpdesk or support phone line if the question is valid for the newer versions as well.  However, we will not answer questions specific to that version.
  • 12.5 is a special case, when we eliminated using J# in the .NET engine. Therefore it is treated as a major version change.
Version Formatting & Layout Exceptions & Failures Security Issues
1 1 November 2003 1 February 2004 1 August 2008
2 1 April 2005 1 July 2005 1 January 2010
3 1 April 2006 1 July 2006 1 January 2011
4 1 December 2007 1 March 2008 1 September 2012
5 1 September 2008 1 December 2008 1 June 2013
6 1 March 2009 1 June 2010 1 December 2013
7 1 September 2009 1 December 2010 1 August 2014
8 1 November 2010 1 February 2012 1 August 2015
9 1 March 2011 1 June 2012 1 December 2016
10 1 April 2012 1 July 2013 1 January 2017
11 1 October 2013 1 October 2014 1 April 2018
12.0 1 March 2014 1 March 2015 1 September 2018
12.5 1 December 2014 1 December 2015 1 June 2019
13 1 October 2015 1 October 2016 1 April 2020
14 1 February 2017 1 February 2018 1 August 2021
15 Released July 2016. Dates to be set when version 16 is released.

Definitions

  • Security issues: A bug that exposes a security vulnerability in your system (this has never occurred to date).
  • Failures: An issue that causes an exception or program failure, and we cannot find a workaround.
  • Formatting and layout: Your output does not match the template.

Microsoft Office

Microsoft drops support for Office 10 years after the release date. So Office 2003 support is ended by Microsoft in 2014. We add one year to that for our support. So end of life for supporting AutoTag on version of Office is:

Version AutoTag End of Support Final AutoTag version
Office 2000 1 January 2012 11.1
Office 2002 1 January 2014 12.5
Office 2003 1 January 2015 13.1
Office 2007 1 January 2019  
Office 2010 1 January 2022  
Office 2013 1 January 2025  
Office 2016 1 January 2028  

Java Engine

  • Starting with version 16, the java engine requires Java 1.7 or later.
  • Starting with version 12.5, the java engine requires Java 1.6 or later.
  • Starting with version 6, the java engine requires Java 1.4 or later.

.NET Engine

  • Version 16 & later, the .NET engine requires .NET 4.5.1 or later.
  • Version 16 & later, the SharePoint lists datasource is gone. Use the SharePoint OData API instead.
  • For version 12.5, the engine API was upgraded to use generics instead of arrays (details here).
  • Starting with version 9.0 the engine is now built under .NET 3.5 instead of .NET 2.0

AutoTag

  • Version 16 & later, the SharePoint lists datasource is gone. Use the SharePoint OData API instead.

Earlier Version Requirements (12.0 and Before)

Java Engine

The Java Engine requires:

.NET Engine

In version 12.5 Windward removed the requirement for J# and has replaced it with IKVM. In Versions 12.5 and later, J# is no longer required.

  • Version 9.0 and later the .NET Engine is compiled under .NET 3.5 instead of .NET 2.0.

The .NET engine requires these drivers for all versions 12.0 and earlier:

AutoTag

  • In version 12.5 Windward removed the requirement for J# and has replaced it with IKVM. In Versions 12.5 and later, J# is no longer required.

    Even though Office 2003 is no longer supported if you're using an older version of AutoTag (pre-12.0) you will need to have the following updates/fixes:

    J# Information (AutoTag/.NET)

    Both AutoTag and the .NET Engine require the J# 2.0 redistributable package from Microsoft for versions 12.0 and earlier. This must be installed after .NET 3.5 is installed as it is an extension of .NET 3.5. It must be installed before installing AutoTag or the .NET Engine.

    You must install version 2.0 - Second Edition, released May 2007.

    Download only the J# appropriate for your O/S

    • J# redist 2.0 (x86) - 32-bit Windows (for Windward version 12 and earlier only)
    • J# redist 2.0 (x64) - 64-bit Windows (for Windward version 12 and earlier only)
    • J# redist 2.0 (IA64) - Intel Itanium Windows (if you have this, you know it -- also for Windward version 12 and earlier only)
  •  
  •  


  •  
  • Was this article helpful?