Printable View
I've made some modifications to the setup1.vbp (installed an EULA) and compiled the new executable. My question is this... why doesn't the installer (setup.exe) require that the vb runtime files first be installed on the end user's machine before my application can even be installed? After all, the setup modifications were done and compiled in visual basic. Am I missing something here? Using Visual Basic 5.0 Pro, SP3. Thanks in advance.
Not sure i understand your question, but here goes.
The reason you need to install the correct VB runtime files and libraries (which ever you use) is in order for your app to run on the End Users comp. For example, if i have a progressbar which is different to windows, ie you can add gradients, and this is a OCX control, i would need to install that on the End Users comp in order for it to work. So you see, its important, no vital that you install them. I think thats based on your question:)
EZapps
By Setup.vbp, I assume you are using PDW? And no, you are not missing anything. That is a good question. But you have to remember one thing...
Just because an app was written by Microsoft does not mean that a newbie did not have a hand in there somewhere or it could be just plain oversight.
It just something that you have to deal with. Since PDW is going to put the files there anyway, it does not bother to check.
Sorry, I guess I didn't make myself clear in my question. I already know that if I create an application using VB5, I must include the runtime files in the setup (installation) program.
As stated in the VB Online Help, the setup program that's included with VB (and used by the Application Setup Wizard or, as you refer to as Package and Deployment Wizard) is setup1.vbp and can be modified as required.
After modifications have been made, you can recompile the setup project to create a new setup1.exe. The Application Setup Wizard will use the new setup1.exe and automatically include the runtime files and/or additional dlls as required and create the final installation program known as SETUP.EXE.
Here's where I get confused. Seeing how the setup project was created and compiled using VB, why doesn't the end user need the runtime files before they can even execute SETUP.EXE? What info or lack of knowledge have I missed?
The reason for my question is this... I made modifications to the setup project and I'm hoping the new SETUP.EXE doesn't crash as soon as the end user tries to execute it.
Thanks Again.
EZapps
The final Setup.exe is probably not using VB. It could actually be written in C or C++. It may actually just be a wrapper, sort of like if you zip a file into an auto-extracting exe.
If that is the case, it would not need any VB functionality or support at all.
If you are not satified with PDW and want to look at anothe installer. I suggest Inno Setup. You can get started with ********** (bottom of post).
Where? :confused:Quote:
Originally posted by randem
...********** (bottom of post).
TomGibbons
You see on my signature (at bottom of my post not thread) where is says Free ....
Or go to http://www.***********/**********.html
Inno Setup is at: http://www.jrsoftware.org
Oh, no I don't actually. I have signatures turned off (due to the horrendously long signatures which some users insist upon).Quote:
Originally posted by randem
...
You see on my signature (at bottom of my post not thread) where is says Free ....
...
Thanks, will check that out when I get home from work.
I appreciate the input, but as for now I will consider the matter unresolved. Hopefully someone can provide a definitive answer.
I think there can only be two ways to use a VB Setup.
If you install an app with the P&D made wizard, you first see a screen that tells you that the various runtime files are being installed. After that the Setup actually starts. That could mean that the Setup.exe app is indeed written in C e.g. and that the VB setup is run only after the runtime files have been copied.
However, if you try to run a VB file on a client PC without runtime files it will obviously not work; but if you place the VB runtime files in the same directory as the app it will work. So the runtime files don't have to be registered. The P&D setup may also use that way to run...
If I understand the situation:
The point he is trying to make is, (for what ever reason) the need for the (VB Runtime) file to exist prior to running of the setup.exe on the end user machine.
Obviously, that scenario dosn't make sense as the installer is picking those up to
be subsiquently installed on the PC at the same time as the app.
Hence, why the need for the existance of the files pre installation.
Is that the issue?
Bruce.
If you have the Dependancy Walker program, you can view which dlls an exe requires. Unlike Setup1.exe, Setup.exe does not require the VB runtime Dll (MSVBVM6.0 or MSVBVM5.0), so it is not a VB program.
Before Setup1.Exe is executed, Setup.Exe first installs all the programs listed in the BootStrap section of the Setup.Lst file.
One more useless note - MS renamed the setup programs to the Package and Deployment Wizard in VB 6.
That sounds like the answer to your question, though I'd like to put in a plug for Inno. It's free (even commercially) and, in my opinion, looks much more professional than the P&D Wizard. Also, it produces one compressed file instead of all that junk from P&D Wizard. It's script-based which makes it more natively powerful, though you can edit the P&D Wizard like you've done. To me, the Inno wizard is by far the easiest. The first setup I made, I got it up and running in around 5 minutes.
Have you ever read the setup.lst file that the pdw creates? Here is part of one from one of my applications . . .
The setup.exe is written in a version of C and this program checks for and installs the VB runtimes and then calls the setup1.exe program (the one you edited and re-complied)Quote:
[Bootstrap]
SetupTitle=Install
SetupText=Copying Files, please stand by.
CabFile=ROEA.CAB
Spawn=Setup1.exe
Uninstal=st6unst.exe
TmpDir=msftqws.pdw
Cabs=1
[Bootstrap Files]
[email protected],$(WinSysPathSysFile),,,7/15/00 12:00:00 AM,101888,6.0.84.50
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,5/31/98 12:00:00 AM,22288,4.71.1460.1
[email protected],$(WinSysPathSysFile),,,6/1/99 12:00:00 AM,326656,4.22.0.0
[email protected],$(WinSysPathSysFile),$(TLBRegister),,6/3/99 12:00:00 AM,17920,2.40.4275.1
[email protected],$(WinSysPathSysFile),,,3/8/99 12:00:00 AM,147728,2.40.4275.1
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,3/8/99 12:00:00 AM,164112,5.0.4275.1
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,4/12/00 12:00:00 AM,598288,2.40.4275.1
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,8/21/00 2:22:54 PM,1388544,6.0.89.64
doh! I should have read though all the posts more carefully! Bruce said what I said before I said it ~brain hurts now~Quote:
Originally posted by brucevde
If you have the Dependancy Walker program, you can view which dlls an exe requires. Unlike Setup1.exe, Setup.exe does not require the VB runtime Dll (MSVBVM6.0 or MSVBVM5.0), so it is not a VB program.
Before Setup1.Exe is executed, Setup.Exe first installs all the programs listed in the BootStrap section of the Setup.Lst file.
One more useless note - MS renamed the setup programs to the Package and Deployment Wizard in VB 6.
Thanks everyone. I think I understand it now. Setup.exe (probably written in C#) first installs the runtime files and then calls setup1.exe. That makes sense to me. Have a good day.
Close!! C or C++Quote:
Originally posted by EZapps
Thanks everyone. I think I understand it now. Setup.exe (probably written in C#) first installs the runtime files and then calls setup1.exe. That makes sense to me. Have a good day.
C# didn't exist when that was created!