Hello Everybody,

I have a few things to say and I hope I broke it down in a way that's understandable.

Background information:
I put my setup.exe files and msi files on a network share and I install it on computers from there. This works perfectly fine until I make changes to my program and subsequently build a new setup and msi. I then overwrite the msi and setup files on the network share.

The problem:
When I try running the program that was installed with the previous install, I get an error and it asks me to browse to the MSI file. This isn't the first program I've written or have done this whole process with, but this is the first time this problem has happened and I have no Idea why.

Questions:
The only thing that I did differently with this setup is that  I changed the version from 1.0.0 to 1.0.1 (I'm using Visual Studio 2008). Is this why I am having this problem? If so, do all programs access the msi file on startup or did I somehow make it do that?

Other information that is possibly relevant:
I am running Windows 7 64 bit Ultimate. My program is targeted to an x86 processor. The program reads and writes to a MySQL database. I've written other programs that do similar things but this is the first one that I wrote that connects to a MySQL database. I also have the 32bit MySQL drivers installed on my computer.

This is happening because you are launching the application using the "Advertised Shortcut" that MSI installs.  What this does is validates the install each time the program is run, checking for MSI files, registry entries, etc.  Since you changed the MSI, the install can't be validated.

Check out this link for more info and ways to disable this:

http://stackoverflow.com/questions/627795/net-app-shortcut-for-msi-when-run-by-regular-user

I used to rock and roll every night and party every day.  Then it was every other day.  Now I'm lucky if I can find 30 minutes a week in which to get funky. - Homer Simpson

Arrrr, mateys!  Ye needs ta be preparin' yerselves fer Talk Like a Pirate Day!  

Thanks Tons!!!

I tired the post build event in the link you posted but it errored out when I built the setup.

What I wound up doing was manually putting this in a command prompt after I built the new setup.


The down side to this is that it runs the MSI, but Advanced Shortcuts is disabled.