|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Setup of a .NET InstallationWe are having great difficulty configuring the 'setup' project in .net and
making it so that it will OVERWRITE and REPLACE previous versions. We have a number of Visual Basic products in our suite, and have built separate Setups for each of them. Ths Setups work fine apart from one little glitch which forces us to do a manual 'Unload' of previous versions. We have set the 'DetectNewerInstalledVersion' flag to True, AND the 'Remove Previous Versions' flag to True, but the installation still will not work unless we go through 'Control Panel-> Add or Remove Programs' first and 'manually' uninstall the previous version. Can anyone tell me what we are missing here as this is holding up our release. Regards and thanks Glyn J Meek > We are having great difficulty configuring the 'setup' project in .net and change version property of setup project...> making it so that it will OVERWRITE and REPLACE previous versions. We have > a number of Visual Basic products in our suite, and have built separate > Setups for each of them. Ths Setups work fine apart from one little > glitch which forces us to do a manual 'Unload' of previous versions. > > We have set the 'DetectNewerInstalledVersion' flag to True, AND the > 'Remove Previous Versions' flag to True, but the installation still will > not work unless we go through 'Control Panel-> Add or Remove Programs' > first and 'manually' uninstall the previous version. > > Can anyone tell me what we are missing here as this is holding up our > release. Change it to a version higher than 1.0.0
I noticed that using 0.0.1 ... did not work properly. Show quoteHide quote "Josip Medved" <jmed***@jmedved.com> schreef in bericht news:codjuf$hqa$1@bagan.srce.hr... > > We are having great difficulty configuring the 'setup' project in .net and > > making it so that it will OVERWRITE and REPLACE previous versions. We have > > a number of Visual Basic products in our suite, and have built separate > > Setups for each of them. Ths Setups work fine apart from one little > > glitch which forces us to do a manual 'Unload' of previous versions. > > > > We have set the 'DetectNewerInstalledVersion' flag to True, AND the > > 'Remove Previous Versions' flag to True, but the installation still will > > not work unless we go through 'Control Panel-> Add or Remove Programs' > > first and 'manually' uninstall the previous version. > > > > Can anyone tell me what we are missing here as this is holding up our > > release. > > change version property of setup project... > > -- > Pozdrav, > Josip Medved, MCSD > http://www.jmedved.com > You're right, VS setup projects start the version at 1.0 and don't upgrade
versions below this with a RemoveExistingProducts. The other thing to watch out for is that an Everyone install won't upgrade a Just me and vice versa. Also the ProductCodes must be different but the Upgradecode needs to be the same. -- Show quoteHide quotePhil Wilson [Microsoft MVP-Windows Installer] Definitive Guide to Windows Installer http://apress.com/book/bookDisplay.html?bID=280 "Gene Vangampelaere" <gene.vangampelaere.remove.t***@infohos.remove.this.be> wrote in message news:uG3iNlh1EHA.2192@TK2MSFTNGP14.phx.gbl... > Change it to a version higher than 1.0.0 > I noticed that using 0.0.1 ... did not work properly. > > > > "Josip Medved" <jmed***@jmedved.com> schreef in bericht > news:codjuf$hqa$1@bagan.srce.hr... >> > We are having great difficulty configuring the 'setup' project in .net > and >> > making it so that it will OVERWRITE and REPLACE previous versions. We > have >> > a number of Visual Basic products in our suite, and have built separate >> > Setups for each of them. Ths Setups work fine apart from one little >> > glitch which forces us to do a manual 'Unload' of previous versions. >> > >> > We have set the 'DetectNewerInstalledVersion' flag to True, AND the >> > 'Remove Previous Versions' flag to True, but the installation still >> > will >> > not work unless we go through 'Control Panel-> Add or Remove Programs' >> > first and 'manually' uninstall the previous version. >> > >> > Can anyone tell me what we are missing here as this is holding up our >> > release. >> >> change version property of setup project... >> >> -- >> Pozdrav, >> Josip Medved, MCSD >> http://www.jmedved.com >> > >
Other interesting topics
garbage collection problem in large linked list
Copy protection for a .NET application Is there anyway to treat ViewState the same as SessionState? Assemblies Working Set .Net Framework in Windows 2003 asp.net newbie XML editor component Hide Directory programmatically 14 million lexicons C:\WINNT\Microsoft.NET\Framework\v2.0.40607 |
|||||||||||||||||||||||