Product End of Life Policies

This article details the past versions of Windward Studios products we support, and to what extent we support them. Please remember that our first recommendation is always to upgrade to the newest version of a product. 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 a Windward Studios product. If you have any questions, please don't hesitate to contact us.

Definitions

  • Security issues: a bug that exposes a security vulnerability in your system
  • 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

Support

End of life dates are listed below for all versions except the current version. Our guidelines for the dates set are:

  • formatting and layout bugs are handled for six months after the release date of the subsequent version
  • exception and failure bugs are handled for 18 months after the release date of the subsequent version
  • security issues are handled for five years after the release date of the subsequent version

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.0 to 11.1.38.0 is not much different from an upgrade from 11.1.38.0 to 12.0.0.0. You get new features while the existing features are unchanged. (The upgrade from version 9 to version 10 is an exception - that has significant changes in how select statements 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 newer versions as well. However, we will not answer questions specific to that version.

12.5 is a special case; at that release we eliminated using J# in .NET Report Engine. Therefore it is treated as a major version change.

Version Formatting and Layout Exceptions and 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 1 April 2019 1 April 2020 1 October 2023

End of life for version 16 will be announced when version 17 is released.  

Product-Specific Notes

Report Designer Office Edition

Starting with version 16, .NET Framework 4.6.1 or later is required.

Java Report Engine

  • Starting with version 12.5, Java Report Engine requires Java 1.6 or later
  • Starting with version 6, Java Report Engine requires Java 1.4 or later
  • Starting with version 16, Java Report Engine requires Java 1.8 or later

.NET Report Engine

  • For version 12.5, the .NET Report Engine API was upgraded to use generics instead of arrays (see [Upgrading to the 12.5 API])
  • Starting with version 9.0 .NET Report Engine is now built with .NET 3.5 instead of .NET 2.0
  • Support for .NET 3.5 ended in version 15.1
  • Starting with version 16, .NET Framework 4.6.1 or later is required

Report Engine for RESTful

Starting with version 16, .NET Framework 4.6.1 or later is required.

Microsoft Office

Microsoft drops support for Office 10 years after the release date, e.g. Office 2003 support was ended by Microsoft in 2014. We add one year to that for our support; hence end of life for supporting Report Designer Office Edition on a version of Office is:

Version Report Designer End of Support Final Report Designer 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
15.2
Office 2010
1 January 2022

Office 2013
1 January 2025

Office 2016
1 January 2028

Earlier Version Requirements (v12 and Earlier)

Report Designer for Office Edition

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.

.NET Report 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.

  • See more details on the conversion at [Upgrading to the 12.5 API]
  • Version 9.0 and later .NET Report Engine is compiled under .NET 3.5 instead of .NET 2.0.

.NET Report Engine requires these drivers for all versions 12.0 and earlier:

Java Report Engine

Java Report Engine requires:

J# Information

Both Report Designer and .NET Report 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 Report Designer or .NET Report Engine.

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

Download only the J# appropriate for your O/S

0 Comments

Add your comment

E-Mail me when someone replies to this comment