Iam having difficulties trying to figure out the bugs in my project. It works just fine and dandy on my machine, but whenever I give the exe to other people, the program just randomly closes without any error messages at all.
How can I debug it?
Printable View
Iam having difficulties trying to figure out the bugs in my project. It works just fine and dandy on my machine, but whenever I give the exe to other people, the program just randomly closes without any error messages at all.
How can I debug it?
Unless you create an installation package using something like Inno Setup any exe moved to a different PC will most likely fail.
What should I include in the setup? It doesn't require any extra ocx files.
I use the P&D Wizard that comes with VB but I don't suggest it any more since it may have some problems with Vista, but in any case like the Wizard I assume that Inno will automatically included what it needs except for standalone items like databases.
So i don't need to include the
Asycfilt.dll 2.40.4275.1 144 KB (147,728 bytes)
Comcat.dll 4.71.1460.1 21.7 KB (22,288 bytes)
Msvbvm60.dll 6.0.97.82 1.32 MB (1,386,496 bytes)
Oleaut32.dll 2.40.4275.1 584 KB (598,288 bytes)
Olepro32.dll 5.0.4275.1 160 KB (164,112 bytes)
Stdole2.tlb 2.40.4275.1 17.5 KB (17,920 bytes)
?
See the documentation on the web for Inno or use the P&D Wizard which will include everything you need automatically (with the exception noted above).
I would think that these installation packages examine your project's .vbp file to determine what external files need to be added to the package. When installed on the recipient's PC the installation package does all the work of registering these compnents.
Inno Setup doesn't automatically detect what you need, but they provide documentation explaining what to do.
There is a link to that documentation (and several other things you may find useful) in our Application Deployment FAQ
And since this is an installation problem I've moved the thread.
Seems like I once used one of these installation packages (can't remember the name and I don't see it around anymore) which did do all the work for you and auto included all the files needed. Also, it was programmable meaning you could make a custom installation package.
NOTE: AFTER POST EDIT
OK, the name was (is) InstallShield
Yes InstallShield is a nice program and I've used it myself when I worked, but it is expensive at $599 for the standard Windows version whereas both the P&D Wizard and Inno are free.Quote:
Originally Posted by jmsrickland
Just as Visual Studio 6.0 Installer 1.1 is, the tool Microsoft released shortly after VB6 as a replacement for the PDW to conform with emerging standards for Windows installations.Quote:
Originally Posted by MartinLiss
The packaging tool: Visual Studio 6.0 Installer
Updated merge modules: Merge Modules for Service Pack 6 for Visual Basic 6.0 and Visual C++ 6.0
How to: How To Create a Visual Basic Installer Package with Visual Studio Installer
Could you please describe how to use this?Quote:
Originally Posted by dilettante
There are some pretty good writeups out there that describe basic use via the Visual Basic Installer Wizard. One of these is Introducing Visual Studio Installer.
Other useful articles might be Getting Started with Visual Studio Installer and Considerations for Choosing Visual Studio Installer.