Packaging and Deployment Wizard

Ok finished my app thanks to some very useful help on this forum - thanks again guys.

Now I have used the packaging and deployment wizard and ended up with a directory called Package that contains setup.exe, a cab file and setup.lst. Also there is a directory called Support containing many files.

Do I need all of these to install my app on another pc or just the setup.exe and cab file?

Also when I ran this on a win 98 pc (VB 6 not installed) the installation program ran ok but at the end said some of the fileswere out of date and needed updating from setup. Anyone got any idea what this is on about?

Cheers

DJ

Visual Studio Installer - 1 file...

1. Yes you need al those files in support.
2. Does it ask you to restart you computer? If so it is becuase it is registerd a few controls that replaced the old ones.

1) All the files are needed.
2) The vb runtime files that are needed are out of date or don't exist. You need these on the pc before you run any vb program, the P&D wizard copies these for you, then installs the app normally after you reboot.

Thanks great I'll try again.

Quote:

---

Also when I ran this on a win 98 pc (VB 6 not installed) the installation program ran ok but at the end said some of the fileswere out of date and needed updating from setup. Anyone got any idea what this is on about?

---

Ceratin system, this becomes an endless loop. That is why I mentioned the VSI. It seems to handle those issues...

Thanks for the pointer - I'll have another crack at installation tomorrow as I'll have a completely clean system to try it on.

VSI? - where is this available?

Visual Studio Installer 1.1 here

Thanks for that James - I might just have to download it (plus SP3 first!).

Seriously guys thanks for all the help.

DJ

Quote:

---

Originally posted by dj4uk
Thanks for that James - I might just have to download it (plus SP3 first!).

Seriously guys thanks for all the help.

DJ

---

SP3? Hell download SP5 ... :)

No, you don't. I guess he's asking if he needs to ship all the "Support" folder. If that's the question, the answer is no.

Quote:

---

Originally posted by Mc Brain
No, you don't. I guess he's asking if he needs to ship all the "Support" folder. If that's the question, the answer is no.

---

That was one of them... :D

To enhanced the information. The Support folder has all the needed files copied in it. Besides, it includes a batch file that lets you recreate the CAB file. So, if tomorrow (or whenever) you re-compiled your app (newer version), you only need to copy this new EXE in the Support folder (overwrite it, obviously) and run the batch file to re-create the CAB. Then.... you have a new CAB with your new EXE and all the needed files.

To sum up, all you need are:

• Setup.exe
• Setup.cab (or whatever its name is -can't remember- )
• Setup.lst

Quote:

---

Originally posted by James Stanich
That was one of them... :D

---

Ok, then... the sentence "1) All the files are needed." seems to give the wrong idea.

Quote:

---

Also when I ran this on a win 98 pc (VB 6 not installed) the installation program ran ok but at the end said some of the fileswere out of date and needed updating from setup. Anyone got any idea what this is on about?

---

This is why I answered. VSI seems to stop the occurances of this. Also allows for one file, which m,akes it quite easy to determine which one to distribute...;)

VSI doesn't create a single file if you really want a setup to be installed in whatever machine. Especially, if this machine hasn't "Windows Installer" installed.

VSI creates one executable file for installation, taht's all I am saying. As far as Windows Installer, well I guess I hadn't thought of that (never has come up before, but good point McBrain).

As far as I can remember, VSI creates these files:

• Setup.MSI (the installer itself)
• Setup.exe (the bootstrap file that will check that Windows Installer is installed and if not, install the proper version of it)
• Instmsiw.exe (the Windows NT/2000 Windows Installer)
• Instmsia.exe (Windows 95/98 Windows Installer)

each of these Instmsi?.exe file is 1.46 (approximatelly... but bigger than a diskette).

Unless you ask to only create the installer, in which case, only the .MSI would be created.

Quote:

---

Unless you ask to only create the installer, in which case, only the .MSI would be created.

---

My point exactly. One file to distribute. Am I not making this clear enough?

Yes you're. I'm just pointing the PROs and CONs of VSI.... but it won't be the only file to distribute for Win9x users who has no Windows Installer installed.

Quote:

---

Originally posted by Mc Brain
Yes you're. I'm just pointing the PROs and CONs of VSI.... but it won't be the only file to distribute for Win9x users who has no Windows Installer installed.

---

As I mentioned good point. I don't want to argue over Install packages here, but you are always pushing Inno. Is this an issue with that package creater?

Quote:

---

Originally posted by James Stanich
As I mentioned good point. I don't want to argue over Install packages here, but you are always pushing Inno. Is this an issue with that package creater?

---

Not at all. I've had some problems with VSI some times. Besides, I didn't like the idea of having to add 3 files (which are 3.5 MB approx. extra) just to be sure that the installer would run on any machine.

Quote:

---

Originally posted by Mc Brain
Not at all. I've had some problems with VSI some times. Besides, I didn't like the idea of having to add 3 files (which are 3.5 MB approx. extra) just to be sure that the installer would run on any machine.

---

So there are no issues with Inno? Maybe I'll make a change, although I really like the inteface. Oh well, enough CC. ;)

No. And the only "issues" i had was because I didn't know how to do something. But there's an active newsletter (through Outlook) where you can ask what you need and get an answer (even Jordan Russell -the author- could answer you).

Oh... and another thing. I don't know if VSI has this, but you can create setups in different languages (downloading the language file to use to create the setup).

You need the .Cab file. the .Lst file and the .EXE file

You don't need what's in the support folder. The reason it's there is so you can modify your EXE and then copy it in the support folder and run the batch to update the cab, lst and such. However, I find it sometimes easier just to run the P & D wizard again so I delete it to save some space

Quote:

---

but you can create setups in different languages

---

Not a problem for me... but interesting. I am more concerned with the lack of the "analyzer" you mentioned...

Quote:

---

Originally posted by sdjunky
You need the .Cab file. the .Lst file and the .EXE file

You don't need what's in the support folder. The reason it's there is so you can modify your EXE and then copy it in the support folder and run the batch to update the cab, lst and such. However, I find it sometimes easier just to run the P & D wizard again so I delete it to save some space

---

I've already said that: ;)

Quote:

---

Originally posted by Mc Brain
To enhanced the information. The Support folder has all the needed files copied in it. Besides, it includes a batch file that lets you recreate the CAB file. So, if tomorrow (or whenever) you re-compiled your app (newer version), you only need to copy this new EXE in the Support folder (overwrite it, obviously) and run the batch file to re-create the CAB. Then.... you have a new CAB with your new EXE and all the needed files.

To sum up, all you need are:

• Setup.exe
• Setup.cab (or whatever its name is -can't remember- )
• Setup.lst

---