P&D Including multiple .exe's in one Package 2

[maxflitom]

Hello Tek-Tips,

I have written an app and wish to use the Package & Deployment Wizard to produce the setup files. I have two .exe files that comprise the application, one is the actual app, the other are data tools ran outside the app.

Instead of creating two setup packages, one for the app and the other for the app's tools, can I compile one setup package to include both exes and have them show in the same start menu as two separate items.

Thanks for all your help,

Tom (maxflitom)

 

[LPlates]

To answer your question... yes.

 

[CassandraR]

Hi Tom:

The method for the first part of your question (can one include a second EXE file) involves adding the file when you get to the PDW dialog form that is captioned "Package and Deployment Wizard - Included Files". On the right side of the form, there is button labelled "Add . . ." that allows you to browse your hard drive to select another file to add to the package.

The method for the second part of your question (adding the additional EXE file to the Start Menu) involves adding the Item on the "Package and Deployment Wizard -- Start Menu Items" form. Click on "New Item . . ." and select the additional EXE file. Clicking Okay takes you back to the "Start Menus Items" form, which now lists the item you just added.

HTH,
Cassie

 

[maxflitom]

Cassie2002,

Thanks for the reply you deserve a star!

I thought that was the way to do it but just wanted to make sure. This is my first compile with multiple exe's in the same setup package.

What I am not sure of is, will P&D know which references I have selected in the project when I add the exe file or will I have to manually select them?

Tom (maxflitom)

 

[CassandraR]

Hi Tom:

Thanks for the star!! And you are very welcome for the help.

When PDW goes to use an additional executable file, it checks for a dependency file for that executable file. It is best to create the dependency file for the extra executable files, using the PDW and selecting "Dependency File" in place of "Standard Installation Package." Do this by bringing up the additional execuatable's project in VB and running PDW. Once you have created the Dependency File, VB can use it when you use the PDW with the main executable packaging.

Cassie

 

[maxflitom]

Thanks again Cassie2002,

I did as you instructed and it works fine. Thanks again for your help!

Tom (maxflitom)

 

[CCLINT]

You also might want to strongly consider FIRST creating with the P&D a dependency file for the SECOND exe.
Then, when the second exe is added, the P&D will check it's dependencies and add them to the package as well, if any dependencies are not in the first exe.

Say you use a DataReport, or DataGrid in the second exe, but not the first exe.
And Say that the first exe uses a FlexGrid, but the sencond doesn't.
The P&D wizard will check for the dependencies for the project it is creating the setup package for, the first exe, automatically, but for the second exe it will just add the exe to the package.

When you run your project on an OS, for instance W9x, where none of these components were ever installed before, you will find that the first exe will run, but the second exe will fail, because the DataGrid and DataReport components were not added to the package and also installed.
Creating a Dependency file will prevent this.

 

[maxflitom]

Thanks CCLINT. I did not create a dependecy file for the second app. I thought there may be a little more than just adding the file to the setup.exe.

Tom (maxflitom)