![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
![]() |
| |
| | #1 (permalink) |
| | MSI Installer VS 2005 Setup Project I was told (I suspect incorrectly) to increment the Version of my setup project every time I build a new MSI or the MSI won't install. When I do that it tells me to change the ProductCode property of the project which I suspect is a bad thing but I don't know any better so I do it anyway. I guess the question is: when should I increment the version of my setup project? And when I do should I change the ProductCode? |
My System Specs![]() |
| | #2 (permalink) |
| | Re: MSI Installer VS 2005 Setup Project "LostCub" <LostCub@xxxxxx> wrote in message news:3193CE6F-322F-4D0C-A0C7-67B0B0A4108A@xxxxxx Quote: >I was told (I suspect incorrectly) to increment the Version of my setup > project every time I build a new MSI or the MSI won't install. your previous MSIs already installed on the system - something along the lines of "This package is already installed on the system". In general, if you are building an installer with some changed files, you _should_ increase the version number. It is, after all, a different version of your application! Quote: > When I do that it tells me to change the ProductCode property of the > project > which I suspect is a bad thing but I don't know any better so I do it > anyway. UpgradeCode. ProductCode is specific to a specific _version_ of your product. If ProductCode for two packages matches, then, as far as Windows Installer is concerned, it's the same package (and then you get the same "already installed" error). So, if you change the version number, you should indeed change the ProductCode. UpgradeCode is more generic, and refers to all versions of your product that can be upgraded from one to another (and typically cannot be installed side by side). When run, if your installer will detect any packages on the system with the same UpgradeCode but smaller version number, it will uninstall them as part of the installation progress - to the user, it will look as an upgrade. And if it detects the same UpgradeCode and higher version number, it will abort installation with a message that a later version is already installed. Quote: > I guess the question is: when should I increment the version of my setup > project? And when I do should I change the ProductCode? |
My System Specs![]() |
![]() |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| Vista Setup Project - Rights Issue | .NET General | |||
| VS 2005 Setup project error with custom dialog | .NET General | |||
| Checking serial key with setup project. | .NET General | |||
| Advertised Shortcuts in a setup and deployment project | .NET General | |||
| Shared Add-in project type template in VB 2005 Express Ed | .NET General | |||