Here's an issue I ran into today in case anyone else has the same problem.

Having updated our components to include versions compiled against .NET 2.0 (beta 2) I added them to the MSI installer using InstallAnywhere.Net. The installer copies the assemblies to the file system and also installs them into the GAC. It was a simple update and ran fine on the test machines I had (Windows XP, 2000 and 2003).

However, I've since had a couple of support calls from people getting an error when the installer is trying to copy some of the files. After a lot of work to reproduce the problem it appears that the .NET 2.0 version assembly causes problems when it is copied to the GAC *if* running on Windows 2003 pre SP-1.

The easiest solution is to add some options to our installer so that the .NET 2.0 version files are not installed by default and are an optional component. It may be useful to also provide the option to install components into the GAC or not fo those who want to have access to the .NET 2.0 versions but who don't have .NET 2.0 (beta 2) installed.