Hi,
Recently I have experienced a problem with Visual Studio .NET Setup
Projects: 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.
Researching this issue in Google I have found some references from other
users experiencing the same problem:
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&c2coff=1&threadm=OO5Q8Z79CHA.
2920%40TK2MSFTNGP11.phx.gbl&rnum=3&prev=/groups%3Fhl%3Den%26lr%3D%26ie%3DUTF-8%2
6c2coff%3D1%26q%3Dmicrosoft.public%2Bmsi%2Bcustom%2Bactions%2Bprevious%2Bversion
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&c2coff=1&threadm=30a27a98.031
1041629.38c873e1%40posting.google.com&rnum=5&prev=/groups%3Fhl%3Den%26lr%3D%26ie
%3DUTF-8%26c2coff%3D1%26q%3Dmicrosoft.public%2Bmsi%2Bcustom%2Bactions%2Bprevious
%2Bversion
http://groups.google.com/groups?q=BUG:+Managed+Installer+class+Upgrade+problem&h
l=es&lr=&ie=UTF-8&c2coff=1&selm=%23x%23qmU%23YCHA.1788%40tkmsftngp12&rnum=1
So, I have just written a MSDN Knowledge Base Community Solutions article
which describes the problem with a step by step to reproduce it:
BUG: Visual Studio .NET Setup Projects Execute Custom Action of Previous
Version when Upgrading:
http://support.microsoft.com/default.aspx?scid=kb;en-us;555184
I would like someone from Microsoft to take a look at it and also I would
like to find a workaround.
Thanks in advance,
Carlos J. Quintero (Visual Developer - .NET MVP)
Felix Wang - 25 Aug 2004 04:14 GMT
Hello Carlos,
I have replied you regarding the same issue in the msi newsgroup
(microsoft.public.platformsdk.msi). If you have time, please go there and
have a look.
Have a nice day.
Regards,
Felix Wang
Microsoft Online Partner Support

Signature
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Dirk Sigurdson - 07 Oct 2004 08:16 GMT
> Hi,
>
[quoted text clipped - 26 lines]
>
> Carlos J. Quintero (Visual Developer - .NET MVP)
Carlos,
My company has fought this same problem and the only way we have been
able to work around it is by renaming the custom action dll. Basically,
something like:
customaction1.dll ... installer version 1.0
customaction2.dll ... installer version 1.1
Dirk Sigurdson
Carlos J. Quintero [MVP] - 07 Oct 2004 08:56 GMT
That was not possible in my case, so I had to switch to another setup
program (InnoSetup).

Signature
Carlos J. Quintero (Visual Developer - .NET MVP)
The MZ-Tools all-in-one add-in, now for .NET: http://www.mztools.com
> My company has fought this same problem and the only way we have been
> able to work around it is by renaming the custom action dll. Basically,
[quoted text clipped - 4 lines]
>
> Dirk Sigurdson