|
|
|
date: Mon, 4 Aug 2008 20:17:01 -0700,
group: microsoft.public.vstudio.general
back
RE: Visual Studio 2008 Setup and Deployment MSI BUG?
Has anyone discovered the solution to this? I just started working with a
deployment package and am experiencing the same thing. Version incremented,
remove previous, everything... nothing seems to actually DO the upgrade.
"Chris T." wrote:
> I have been using setup and deployment projects for years and have never had
> this problem.
> I have created a Visual Studio 2008 setup and deployment project to package
> several C#.NET windows applications with C#.NET class library dependencies,
> all projects in the same solution.
> I've tried referencing both the "primary project output" for two of the win
> forms applications and also the exe files directly.
> I can create an installer .MSI file without a problem, and it installs
> correctly, however upgrade installs do not work correctly. I increment the
> version number (of course allowing VS to update the product code) and build
> the MSI again. When this MSI is installed on a computer that has a previous
> (lower version) of the same software (same upgrade code) the install runs
> without error, but upon completion the application's install folder still
> contains the files from the previous installation.
> I've tested upgrading software on several computers using XP and Vista, each
> experiences the same problem.
> If the previous version of the application is uninstalled first, then the
> new MSI is installed the NEW versions of the application files ARE installed
> to the application folder...so the MSI obviously contains the new app files.
> I can't believe this is a bug as I've only found 1 post from someone else
> who has experienced this problem with VS2008 back in February; naturally with
> no resolution.
>
> Installer options
> DetectNewerInstalledVersion=true
> InstallAllUsers=true (always has been)
> RemovePreviousVersions=true
> Version incremented each time and allowing VS to generate a new product code.
>
> If anyone could shed some light on this I would greatly appreciate it.
>
> Thanks,
>
> -Chris
>
>
date: Sun, 12 Oct 2008 06:06:01 -0700
author: Joe R Joe
RE: Visual Studio 2008 Setup and Deployment MSI BUG?
Me too... very frustrating. Seems like this should just work. Increment
version, let productcode change and everything I read says that should do
it... Does it matter which part of the version I'm changing? I'm just
changing the last digit after the 2nd decimal point.
"Byrnes" wrote:
> I have this exact same problem and would *love* to know how to get this
> working correctly. My setup properties are identical, as are my results.
> What exactly is needed to be done in order for an .msi installer to
> successfully upgrade a previous version? (I'm on VS 2008 SP1 even...)
>
> I'm on the edge of my seat here...
>
>
> "Chris T." wrote:
>
> > I have been using setup and deployment projects for years and have never had
> > this problem.
> > I have created a Visual Studio 2008 setup and deployment project to package
> > several C#.NET windows applications with C#.NET class library dependencies,
> > all projects in the same solution.
> > I've tried referencing both the "primary project output" for two of the win
> > forms applications and also the exe files directly.
> > I can create an installer .MSI file without a problem, and it installs
> > correctly, however upgrade installs do not work correctly. I increment the
> > version number (of course allowing VS to update the product code) and build
> > the MSI again. When this MSI is installed on a computer that has a previous
> > (lower version) of the same software (same upgrade code) the install runs
> > without error, but upon completion the application's install folder still
> > contains the files from the previous installation.
> > I've tested upgrading software on several computers using XP and Vista, each
> > experiences the same problem.
> > If the previous version of the application is uninstalled first, then the
> > new MSI is installed the NEW versions of the application files ARE installed
> > to the application folder...so the MSI obviously contains the new app files.
> > I can't believe this is a bug as I've only found 1 post from someone else
> > who has experienced this problem with VS2008 back in February; naturally with
> > no resolution.
> >
> > Installer options
> > DetectNewerInstalledVersion=true
> > InstallAllUsers=true (always has been)
> > RemovePreviousVersions=true
> > Version incremented each time and allowing VS to generate a new product code.
> >
> > If anyone could shed some light on this I would greatly appreciate it.
> >
> > Thanks,
> >
> > -Chris
> >
> >
date: Wed, 15 Oct 2008 08:03:01 -0700
author: Randy Jean Randy
|
|
