Deploying VB app without package

[vdraceil]

I recently saw a game developed with VB.It just has an exe with some DLLs and support files(pic n sound files) inside a folder.
It runs without installing anything to the computer.
A package with all those files must require a larger disk sapce than this one.
So,does anybody know how to do this kind of application distribution/deployment?

[Keithuk]

I recently saw a game developed with VB.It just has an exe with some DLLs and support files(pic n sound files) inside a folder.
It runs without installing anything to the computer.
A package with all those files must require a larger disk sapce than this one.
So,does anybody know how to do this kind of application distribution/deployment?

Well this will depend on what additional ActiveX's your app uses. If it only uses the standard controls on the VB6 Toolbox then all you need is the VB6 RunTime Files mainly msvbvm60.dll. If you app is going onto a Win2k/XP/Vista system then they are installed as standard.

If your app uses additional ActiveX's e.g. comdlg32.ocx then it maybe on the users system if not then you will have to include it in your own simple package along with a ReadMe note telling the user where to put this file, Win\Sys. Don't worry about registering the ocx there is no need when your app is running. It only has to be registered when you use it in VB IDE.

You haven't said if your app uses any additional files e.g. help files, pictures, text files etc. You could included these in a Resource file and use them from in there. The only thing you have to remember with this is it increases the compiled exe size by the same amount as the filesizes added.

[vdraceil]

In the game which i have all the necessary dlls and other files in the same folder..doesnt that mean it is not necessary to put the dll files in win/sys32 folder?
(if it is mandatory to put the dlls in such folders,then i suppose a package is a must)

[Keithuk]

In the game which i have all the necessary dlls and other files in the same folder..doesnt that mean it is not necessary to put the dll files in win/sys32 folder?
(if it is mandatory to put the dlls in such folders,then i suppose a package is a must)

It depends how these dll's are called for. As a general rule they should all be in the Win\Sys32 folder. What the installer should do it check if this dll is already in the Win\Sys32 folder and if its older than the date of the newer one you are trying to install.

The advantage of installation packages is it put all the files in the correct place. I've said it before in your other topic on this subject. I wouldn't bother with P&D Wizard because its 10 yeas old now. I would opt for Inno Setup because you can have problems installing in Win2k/XP/Vista with P&D Wizard.

[vdraceil]

Then hw does that game run with all its dlls in its app folder??