Archive: Nsis _ Vb Installer??


Nsis _ Vb Installer??
is there a tool or something that will allow me to use NSIS as a VB Project packager, instead of the Packagae & Deployment Wizard?

Id like to pack my Installer files using NSIS instead of the standard VB tool.

Has anyone done this, or know of a tool to do it??

Cheers

James Tanner


As far as I know isn't there any program that could replace the Package and Deployment wizard. No program that I have seen can read the vbs-files and create a setup out of them.


Well you can make the hole
process by your self.
That means to have to know all
the files req. by your app (ocx, dll, etc).
Read Manual, check the examples, make your app
and... pump up :)


Yeah, I make VB programs. All you need to do is check what runtime files it needs and include them along with the .exe compiled file and any other support files. :)


Need help to build one?


make the installer through the package and deployment wizard and then extract the cab file and you have all the files you need. There is also some hints somewhere around here on how to install the vbruntimes (which can be silent).


Many thanks for all the help people, i was hoping there would be a quick and easy way of doing it, oh well, on with the slightly longer & harder war :(


It would be nice if the wizards out there were helpful in installing and adding VB runtime files. Maybe for the next Slate Blue.... ;)


I do this at one point (I also need mscomctl.ocx)


Section "VB Runtime DLLs" SecVBRuntimes
SectionIn 1 4
Setoverwrite off
Setoutpath $SYSDIR
File "C:\Dev\mscomctl.ocx"
RegDLL $SYSDIR\mscomctl.ocx
setoutpath $TEMP
File "C:\Dev\vbrun60sp5.exe"
SectionEnd


then later I do this:

Section "-Install VB Runtimes"
IfFileExists "$TEMP\vbrun60sp5.exe" ""
Exec "$TEMP\vbrun60sp5.exe /q"
SectionEnd

Um, shouldn't it be like this:


Section "-Install VB Runtimes"
IfFileExists "$TEMP\vbrun60sp5.exe" 0 +2
Exec "$TEMP\vbrun60sp5.exe /q"
SectionEnd


The current code you have (IfFileExists "$TEMP\vbrun60sp5.exe" "") is useless, and won't do anything!

-Stu

Originally posted by jtanner
Many thanks for all the help people, i was hoping there would be a quick and easy way of doing it, oh well, on with the slightly longer & harder war :(
Well, considering that you've spent all that time writing the program, a couple of hours ensuring the install works well, will certainly pay off in the long run.

I would use the PDW to create a dependency file (.DEP) so you can see which files are needed for your app, then collect them together manually and use NSIS from there...

I would also, as others have shown, use the VBRun60SP5.exe (or the files contained) for your VB6 Runtimes, rather than using the files generated with the PDW into a the CAB file: if the PDW did a good job of pulling together all the files you need, you wouldn't be here ;)

For information about installing the VB6 runtime, see:

http://nsis.sourceforge.net/archive/....php?pageid=47


Hello all,
I use the Inno setup compiler.
For VB just use the PDW to get all the files needed for your app then import the files into Inno.
It is fast, nice looking and quick way to turn any programming language into a setup file. It has a file import wizard and options for importing any text file for license in the setup. just tell the setup what file you want it to execute when the user clicks finish and it opens it. This will install your app to (C:/Program files) folder and create desktop icons, start menu folder, and quick launch icon.
If you want to check it out here is the link to the site.
http://www.jrsoftware.org/isdl.php


Then you can use this ISS to NSI converter to get an NSIS script :D


Thanks sunjammer, that works great.