There is a Bug in Visual Studio .NET Setup Projects, that causes older version of Custom Actions dll to run during the upgrade:
"When you execute a setup created by a Visual Studio .NET Setup Project to upgrade an application and the setup includes a custom install action, the installer doesn't execute the custom install action of the new version but the one of the previous version, which is being replaced."
When the code in Custom actions changes from one version to another - you have a problem upgrading. The same is happening in both Visual Studio 2003 and Visual Studio 2005. I think this bug is critical and should be fixed ASAP. Fortunately there is a workaround - renaming custom actions dll each time we change its code will force installer to run the new code.
Friday, August 04, 2006 8:16 AM