I have made a deployment package in visual basic 2008 which works fine, except that after the initial setup.exe is run it closes and it may take 30 sec to 2 min for the msi to finish downloading and run(depending on internet speed). Anyone installing the program would think it was not running and click the setup button again. The result is that there are 2 or 3 installation going at the same time
Thanks in advance for any help
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


IIRC, the prinicpal purpose of the set-up stub created by VS is to check that the Windows Installer service is installed and install it if it's not present. Consequently, for installation purposes, you can bypass the stub and run the MSI directly.

BTW, if you're serious about producing professional installation programs, you'll want to abandon VS and use a proper authoring tool. There are really only 2 choices (one, if you tacke my scepticism on board), viz. Symantec/Altiris's Wise and Flexera's InstallShield. Whilst I prefer Wise in day-to-day usage, Altiris's failure to keep up with technology over the last few years means that in all consciousness I can no longer recommend it. As they say on the BBC these days, "other packaging producs are available" but these are the 2 "biggies".

Lastly, this particular forum is designed to be used in connection with errors returned by the Windows Installer engine (for examples, see the 'MSI Errors' link at the top of the page. Your question would have been best posted in the 'Package Development' forum. A moderator may therefore move this thread.
Answered 08/02/2010 by: VBScab
Red Belt

Please log in to comment