Below you will find lifecycle information on all Infragistics products.

NetAdvantage

Infragistics’ NetAdvantage follows a subscription model, and therefore product lifecycle expectations adhere to the following general rules (subject to change, applies only to Windows Forms and ASP.NET elements):

Product Maintenance Expiration of NetAdvantage .NET products = Release date + expected date of 3 future releases (roughly one year from release date)

Product Support (Developer Support) Expiration of NetAdvantage .NET products = Release date + 3 years

NetAdvantage CLR 1.x Products

Infragistics has released new features in NetAdvantage for .NET 2007 Volume 1 with CLR 1.x and 2.0. NetAdvantage for .NET 2007 Volume 1 is the final release of our NetAdvantage for .NET product to be compiled against .NET Framework 1.x. Developer Support is available for these products, and product maintenance is available for the published lifecycle of Release date + expected date of 3 future releases (roughly one year from release date).

Infragistics will continue to release new features and products within NetAdvantage for .NET, compiled for .NET Framework 2.0. Focusing on compiling for .NET Framework 2.0 will allow Infragistics provide new products and features which will leverage .NET Framework 2.0 technology to the fullest degree possible.

NetAdvantage COM Products

As of our 2006 Volume 1 release, Infragistics no longer includes our COM products in NetAdvantage. Prior to that, our COM (previously UltraSuite) tools were included with the purchase of our NetAdvantage product as a separate and optional installation. These COM controls do not fall under the umbrella status of the NetAdvantage Lifecycle they were purchased with. Our UltraSuite COM products have been retired as of October 2005, and are therefore provided "AS-IS" to customers owning licenses of NetAdvantage prior to the 2006 Volume 1 release but are not available with 2006 Volume 1 and above. These are not eligible for product support or maintenance. As such, you will note within the Product Lifecycle data that a NetAdvantage version may have a parent status of Active but an asterisk indicates that not all listed elements are Active (UltraSuite COM products specifically).

TestAdvantage for Windows Forms

Infragistics TestAdvantage follows a subscription model, and therefore product lifecycle expectations adhere to the following general rules (subject to change):

Product Maintenance Expiration of TestAdvantage HP QTP Wrappers = Release date + expected date of 4 future releases (approximately 16 months after release date, refer to posted dates for specifics)

Product Support Expiration of TestAdvantage HP QTP Wrappers = Release date + 3 years

Note:  If you are uncertain as to whether or not maintenance and/or support is available for your specific product, please send an email to registrations@infragistics.com and we will be happy to clarify any points of confusion or concerns for you. When emailing us, please remember to include your Infragistics .dll name and major/minor build number so we can accurately respond with additional information or clarification.

Definitions of Terms:

Product Maintenance - Refers to bug fixing and all other development work requiring code recompile for the product or the install. Expected Product Maintenance Expiration dates are posted unless the date has passed, in which case the Product Maintenance Expiration column will display Expired. If your product has a status of "Extended" but the Product Maintenance Expiration has already passed, please refer to the definition of Extended status.

Product Support - Refers to product support services (developer support) availability. Expected Product Support Expiration dates are posted unless the date has passed, in which case the Product Support Expiration column will display Expired. When Product Support has gone out of scope for a product, the product is then considered a Retired product, and will also display Retired in the Status column.

Expired - When Expired is shown in the Product Maintenance Expiration column for a product, product maintenance is no longer available for that product. Please note: The product may still be an Active product, however. Refer to Product Status definitions.

If a bug is reported for an Expired version, we will first determine if the bug is fixed in the final hotfix build for that version. If it is not fixed, we test against the latest versions of that product which are eligible for product maintenance and fix the bug in those versions, if found to be present. The fix is available only to licensed users for that version, however, therefore the customer may have to purchase a product upgrade to obtain the fix, unless the customer has a subscription covering the fixed version. Some exceptions exist, therefore we recommend you speak with your salesperson or correspond with your support engineer if you’d like to explore possible options regarding your specific case.

How To Determine the Version of your Infragistics Product

Find Your Product:

To find the specific product you are looking for, browse the Excel file to find the exact file name for your .dll or .ocx.
Please note: The product version in the grid represents the version of the latest release or update, but does not take into account Hot Fixes. If you need assistance in determining the name and version of a specific Infragistics tool please refer to instructions below.

Determine the Infragistics Product Name and Version

Using VS.NET?
The quickest way to determine the version of a specific element is to place any of its controls on a form and locate the elements DLL under "References" in the Solution Explorer window.
Next, Right-click the reference and select "Properties" from the context menu. In the Properties window, the version is displayed in the Version property.
The Version includes everything before the second period and the Build is the numbers after the second period.

Using Visual Basic 6?
Simply place any of the component's controls on a form and click the "..." button to the right of the About property in the Visual Basic property sheet.
The Version will follow the word "Version" and the Build will appear after the word "Build."

Not currently using these development environments?
First, locate one of the component's DLL or OCX files using Windows Explorer, right-click the filename, and select Properties. Then click the Version tab.
The Version appears after the words "File Version" and includes everything before the second period. The Build is the numbers after the second period.

Download Infragistics Product Lifecycle Schedule (PDF Format)
Download Infragistics Product Lifecycle Schedule (Excel Format)