[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.dotnet.framework.setup

Pervious Custom Installer is exicuted on ReInstall's Install event

Spidy

10/24/2006 6:14:00 PM

Tool used VS2005,
Created a Setup project with RemovePreviousVersions to true. The custom
Installer message box pops up a version number as 1.0.0. during install event.

Installed this version.

Changed the version number in the setup project properties and allowed the
ProductCode to be changed automatically. Changed the cutom installers message
box to pop up version number as 1.0.1.

Installed new version with out uninstalling the previous version.
The message box pops up with version number as 1.0.0 on install event.

I was expecting the new custom installer invoked on install event. (on
uninstall event pervious version invoked)

Is this the correct behavior? I hope not, then what is that I am missing.
2 Answers

Phil Wilson

10/24/2006 8:11:00 PM

0

Does this describe your issue?
http://support.microsoft.com/kb/90...
--
Phil Wilson
[Microsoft MVP Windows Installer]

"Spidy" <Spidy@discussions.microsoft.com> wrote in message
news:394EE2C7-4ED1-4D3E-9416-4587A32FBDAD@microsoft.com...
> Tool used VS2005,
> Created a Setup project with RemovePreviousVersions to true. The custom
> Installer message box pops up a version number as 1.0.0. during install
> event.
>
> Installed this version.
>
> Changed the version number in the setup project properties and allowed the
> ProductCode to be changed automatically. Changed the cutom installers
> message
> box to pop up version number as 1.0.1.
>
> Installed new version with out uninstalling the previous version.
> The message box pops up with version number as 1.0.0 on install event.
>
> I was expecting the new custom installer invoked on install event. (on
> uninstall event pervious version invoked)
>
> Is this the correct behavior? I hope not, then what is that I am missing.
>


Spidy

10/24/2006 8:28:00 PM

0

Yes it does. The work around (stated below and in the article) makes sense, I
will try that.
To work around this behavior, sign the assembly that contains the new
version of the setup project by using a strong name.

http://support.microsoft.com...

"Phil Wilson" wrote:

> Does this describe your issue?
> http://support.microsoft.com.../en-us
> --
> Phil Wilson
> [Microsoft MVP Windows Installer]
>
> "Spidy" <Spidy@discussions.microsoft.com> wrote in message
> news:394EE2C7-4ED1-4D3E-9416-4587A32FBDAD@microsoft.com...
> > Tool used VS2005,
> > Created a Setup project with RemovePreviousVersions to true. The custom
> > Installer message box pops up a version number as 1.0.0. during install
> > event.
> >
> > Installed this version.
> >
> > Changed the version number in the setup project properties and allowed the
> > ProductCode to be changed automatically. Changed the cutom installers
> > message
> > box to pop up version number as 1.0.1.
> >
> > Installed new version with out uninstalling the previous version.
> > The message box pops up with version number as 1.0.0 on install event.
> >
> > I was expecting the new custom installer invoked on install event. (on
> > uninstall event pervious version invoked)
> >
> > Is this the correct behavior? I hope not, then what is that I am missing.
> >
>
>
>