NetAdvantage for .NET Contents:

This release of NetAdvantage for .NET contains the following controls and components:

(Note: The NetAdvantage for .NET install contains both ASP.NET and Windows Forms controls, the NetAdvantage for Windows Forms install contains only Windows Forms controls, the NetAdvantage for ASP.NET install contains only ASP.NET controls, while the NetAdvantage AppStylist install contains only the NetAdvantage AppStylist application.)

 

NetAdvantage CAB Extensibility Kit™:

The NetAdvantage CAB Extensibility Kit is an add-on to the NetAdvantage Windows Forms (CLR 2.0) product. This add-on allows your NetAdvantage Windows Forms toolset to interoperate with the Microsoft Composite UI Application Block (CAB) framework.

For more details on the NetAdvantage CAB Extensibility Kit, refer to the “NetAdvantage CAB Extensibility Kit” section in the NetAdvantage Windows Forms help. This help section is located in the following section: Developer’s Guide > The Toolset.

 

Installation Notes:

1.      This installation will stop and restart IIS in order to install the ASP.NET assemblies, scripts, and virtual folders.  This is a DEVELOPER installation package.  Please do not use this install to deploy.  Read the product help and follow the deployment topics.

2.      In order for the ASP.NET samples to run correctly on the Windows Server 2003 operating system, permissions need to be granted to the IIS Worker Process.  This can be achieved by granting the IIS_WPG user account full access to the following subfolders of the NetAdvantage install folder:

a.      ASP.NET\Samples\Data

b.      ASP.NET\Samples\CS\WebCharts\ChartImages

c.      ASP.NET\Samples\VB\WebCharts\ChartImages

3.      If you install any combination of the NetAdvantage for .NET installs and remove one of them at a later time, this might result in known issues. To resolve these, please re-install the appropriate NetAdvantage for .NET install needed.

4.      NetAdvantage AppStylist Style Library Files: If you modify one of the installed Infragistics Style Library (*.isl) files and wish to save the changes for later, ensure that you save your changes as a different file. This will ensure that your customized .isl files are not overwritten by a NetAdvantage hot fix or removed during a NetAdvantage uninstall.

5.      Side-By-Side Help Installations: If you install multiple versions of the NetAdvantage product (e.g., ProductVersion A [NetAdvantage 2006 Volume 2 CLR 1.x] and ProductVersion B [NetAdvantage 2006 Volume 2 CLR 2.0]), you should be aware of the following:

a.      The help that is installed with the product that you install last overrides the help of the previously installed product. For example, if you install ProductVersion A, then ProductVersion B, the help of ProductVersion B overrides the help of ProductVersion A.

b.      You can reinstall the help of another product version by uninstalling and reinstalling the product. For example, if you install ProductVersion A, then ProductVersion B, the help of ProductVersion B overrides the help of ProductVersion A. To obtain the help of ProductVersion A, uninstall and reinstall ProductVersion A. The ProductVersion A help will override the ProductVersion B help.

c.      To view multiple versions of the NetAdvantage help, you can view the online help on the Infragistics website.

 

.NET Framework Compatibility:

All included assemblies have been built against the Microsoft .NET framework 2.0 RTM build. You must have the 2.0 RTM build of the framework installed for the product to work.

 

Version Numbers Description:

After careful input from our development team and Enterprise customers, we have modified our version number system starting with the 2003 Vol. 3 release.

Because of issues with versioning in .NET, the system uses a couple of parts.  To avoid issues with side-by-side versioning, the GAC file names contain the major version as part of the file name. 

Examples:

Infragistics2.Win.UltraWinGrid.v3.dll
Infragistics2.WebUI.UltraWebNavigator.v3.dll

The 2 is used to indicate a CLR 2.0 compatible assembly.

The .v# in the file name is used to indicate a major new version.

The current system of version number will be changed to allow customers to easily tell a large volume of information from the version number.  The first digit will contain the major version number of the control.  This is different from the volume number of the entire toolset because not every control is modified in every release.

The second digits are for minor revisions to the control and will be used to denote minor modification to a control that does not reach the level of a major release but are greater than a hot fix, such as an addition of a handful of properties, methods, or events.

The third set of digits is for the year and volume number that control was last released in.

The final set of digits is the build number.  This is increased each time a build is dropped to our internal QA area.  Not all of these builds are sent out to customers.

The final set of digits also easily notifies you that this is a full regression tested build or a hot fix.  If the build number starts with 10X, it is not regression tested and is a hot fix build.  If the build does not start with 10X, it is a fully tested release.

Examples:

4.03.20043.5 = Beta 1
4.03.20043.10 = 5 drops later Beta 2
4.03.20043.11 = 1 drop later 2004 Volume 3 volume release
4.03.20043.1012 = 1 drop later First hot fix
4.03.20043.1017 = 5 drops later hot fix
5.01.20051.3 = Beta 1 of next volume release with major new features

 

© Copyright Infragistics, Inc., 2001-2006
Infragistics, Inc., Windsor Corporate Park, 50 Millstone Road, Building 200 - Suite 150, East Windsor, NJ 08520 USA
Voice (609) 448-2000, Fax (609) 448-2017, http://www.infragistics.com