views:

49

answers:

3

I have been asked to fix a small problem with one of our small product's install. Its a basic .msi file (about 0.5 megs) that was created in Microsoft Visual Studio. When you run the installer it goes and installs the program, just like it should, then when the progress bar is about 99% done the program that it installed loads up, stalling the installer.

If I go and Exit the running program the installer then finishes and lets me exit. If I dont exit the program I have to go into task manager to exit the installer's process.

I have searched everywhere for a solution to this and I cant find anyone else with a similar problem. I have gone though the code and I cant find anything that would be causing this. Is it just a stupid setting that I am missing?

Sorry for being so vague, I don't know what information is relevant. Thanks!

A: 

Does the program have some form of self registration that it needs to perform.

Installer Blocks inside it etc.

Check what it does when you run InstallUtil against it.

Paul Farry
The Program is very basic. I am still not too experienced with VB.net, but there does not seem to be any self registration.How would I go about using InstallUtil? (first job out of school.. Time to really learn!)
Ian Kremer
Bring up a .NET command line then run installutil /?it will give you all the usagebut basically you run InstallUtil /LogFile=sdjfdsajfsaj.txt PathToYourProgram this can be used for debugging any installblocks inside your program.You can also wire up your Program to use in the Debug Options of your program . Start External Program (installutil).. Command Line Args = path to yourself
Paul Farry
+1  A: 

What's happening is this:

The installer is set up to run the application as part of the install process. This is wrong, because then the installer can't move on to the next part of the install (which happens to be finishing everything up and exiting the installer) until the current part is finished. In other words, the install won't finish until you exit the app.

You want to run the application after the install has been committed - see here for details.

Anon.
A: 

Refer the documentation on Custom Action Return Processing Options, your setup is waiting for an error/success return code after running your application. You need to update the custom action that is launching your program to ignore the return code and not wait for execution to complete.

sascha