VSIP Corroboration

“Be sure to read the EULA” - John Tobler

Yes, definitely. There is a clause in there that says you are OBLIGATED to upgrade your code within 180 days of a new VS.NET release to be compliant with that release.

4. OBLIGATION TO UPGRADE ELIGIBLE PRODUCTS.

To the extent that You continue to distribute Eligible Product(s), You shall begin making available for licensing to End Users through Your normal channels of distribution new, updated versions of all such Eligible Products no later than one hundred eighty (180) days after the date that We commercially release each new version of Visual Studio .NET Technology. Such new, updated Eligible Products shall include a reasonable level of support for and integration with new features and functionality included in new versions of the Visual Studio .NET Technology. You further agree that You shall distribute updates or service pack releases for Your Eligible Products no later than one hundred eighty (180) days after the date that We commercially release an Upgrade for the Visual Studio .NET Technology. Each of Your update(s) and/or service pack release(s) shall include a reasonable level of support for new features, bug fixes and other incremental changes in Our Upgrades. Nothing contained in this Section shall prevent You from distributing old versions of Your Eligible Products to End Users that do not desire to upgrade to new releases of Your Eligible Products.

 For some people, like Frans, this may be a problem.

Also, note that the installation modifies your VS.NET installation to show VSIP status. I'm not sure what this does to distributed components, but I'm about to find out in a few hours, when I send the GenX.NET final build to our beta testers.