Using the Setupfactory Packaging program



Setup factory ways to package your own software development (including installing the dongle driver and OCX registration)

Software: Setup Factory7.0 English version

Previously used the Install Shield 9.0 package VB software, also used VS2005 packaging software packaging VS2005 software, also used InstallShield6.2 to package VB software.

no doubt, whether it is packaged VB or C # developed software, Setup Factory7.0 packaging is the fastest, but also the best, and easy to get started. Once you have it, there's nothing to ask! Thanks to the help of MR.WU, he used it n years ago, or by my rookie to write a summary of it.

The objects we want to pack are: Figure 01

A QQ Go format conversion program, it needs to use the common dialog box Comdlg32.ocx control, we simulate a DogInstallVir.exe software Dog installation applet, no virus, please rest assured. Test.wgs is the go format of QQ, OUT23.SGF is a successful example after conversion.

First, after installing the Setup Factory7.0 English version.

After you click Create, Figure 02:

Figure 3 Select all files for packaging:

The following is the selection of the installation background, you can not choose, you can also get a mm picture ..., Figure 4:

Figure 5:

Figure 6 Select language:

Figure 7 Select VB version:

Figure 8:

After importing all the files, Figure 9:

There are 2 difficulties:

1 . COMDLG32. The OCX control should be placed under C:\windows\system32\, and the software will not be uninstalled when it is uninstalled, otherwise the software may not be used.

2 . How the software Dog (or other executable exe applet) installs before the installation is complete.

Double-click Comdlg32.ocx, and then modify the destination property to:%systemfolder%,10:

Below this is lets uninstall the software the time does not delete the OCX file, can use the shift batch to modify, is very convenient. So if other software also use this OCX, uninstall this software does not affect the other software. Figure 11:

Setup factory automatically creates a shortcut to the "start"-"Programs"-"Software name" folder for all EXE files. Software Dog driver is not necessary to put in "Start"-"program" here, because it is not commonly used. So we make the following changes: Remove the "Start menu > Appfolder" tick. Figure 12:

Set the driver for the dongle below and run the Instdrv.exe executable before the installation is complete. Figure 13:

Figure 14:

Figure 15 Select File-run

Results show 16:

Browse the file, Figure 17:

The following Waitforreturn select True so that the interface to complete the software installation must be installed or not installed. Figure 18 is the interface returned:

After you click "Finish". Figure 19:

After clicking "OK", return to main interface, main program 20:

Figure 21:

Save the project, preferably with a packaged file in the same place, figure 22:

Then click "Publish"-"build" or F7, figure 23:

Figure 24:

Click "Build". Figure 25:

When you are finished, generate the following file, Figure 26:

After running Setup.exe install software, look at the interface, figure 27:

Figure 28:

Figure 29:

Figure 30:

Figure 31:

Figure 32:

Figure 33:

Figure 34:

The Start menu will have automatic unloading, figure 35:

If you are packing C # or C + +, you need to package the framework. More than 20 m. Follow the below to get it right:

1. Add the Net Framework 2.0 (for example, Dotnetfx2.0.exe) to the "original file" in "Resources"
2. Add the following code to the "Start" of the "operation":
result = Registry.doeskeyexist (HKEY_LOCAL_MACHINE, "software\\microsoft\\. Netframework\\policy\\v2.0 ");
if (result = = False) Then
result = File.run (Sessionvar.expand ("%templaunchfolder%\\dotnetfx2.0.exe"), "" "," ", SW_SHOWNORMAL, True);

End

Additional 2 complex Large program packaging problems encountered (2011.01.23 by Kiseigo):
1. How to know which DLL is required for your *.vbp project
2. Why is it always unusual to install "go setup.exe" to a newly installed XP computer?

Answer 1:

Use scan file Dependencies and Scan Visual Basic project under Tools, which requires specifying the full path to your VBP project, and then Setup factory to find the required DLLs and OCX files. It's usually found in "C:\WINDOWS\system32", and then you go down there and copy these files to "under the original files for packaging", create a new folder called "DLLimport", and copy all the DLLs and OCX to the bottom.
They are installed by default to "C:\Program files\ go \dllimport", so you need to correct the value of their destination install to "%systemfolder%", can be modified in batches, The method is to select multiple DLLs, right-click, and then properties, tap the pen button:

Answer 2 :
all the Used DLL and the OCX All need a sentence to register manually, or install good Setup After you start the program, a variety of exceptions occur.


The following is the registration code for the second article:
Shell.execute ("regsvr32", "open", Sessionvar.expand ("/s%systemfolder%\\comctl32.ocx"), "", Sw_ Shownormal);

Using Setupfactory Packager