Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
What is the best installer to use. 2
- Thread starter JohnStep
- Start date
Nothing, as far as I can tell, Eric. After my disappointing brush with Install Shield, I'm beginning to cherish the simplicity of the Package and Deployment Wizard.
Why should Setup have to modify the registry or distribute files to various places on a hard drive? A smart app can do that on the first run.
Still... there are occasions when an "unattended" or "silent" install would come in handy....
Alt255@Vorpalcom.Intranets.com
Why should Setup have to modify the registry or distribute files to various places on a hard drive? A smart app can do that on the first run.
Still... there are occasions when an "unattended" or "silent" install would come in handy....
Alt255@Vorpalcom.Intranets.com
I was in a situation where I had to compile the app, modify the (physical) EXE with another app and then add it back into the distribution.
I think Wise (at least the version I had) would require that your modification step be performed before you started packaging. IOW, it had no capability for a "Pre-package" or "Post-package" step to be defined.
If you were modifying the EXE as part of the application (like, tweaking the EXE to insert a serial number or something), Wise does support this, but I've never done it. I think it requires writing a custom "C" Dll to insert your info in the correct spot in the EXE.
Wise has the ability to extend the setup program by writing a "C" DLL, which I've done. Pretty straightforward, and you have access to all the variables in your Wise script. So you potentially have the ability to do nearly anything that can be done from inside a DLL.
Chip H.
I think Wise (at least the version I had) would require that your modification step be performed before you started packaging. IOW, it had no capability for a "Pre-package" or "Post-package" step to be defined.
If you were modifying the EXE as part of the application (like, tweaking the EXE to insert a serial number or something), Wise does support this, but I've never done it. I think it requires writing a custom "C" Dll to insert your info in the correct spot in the EXE.
Wise has the ability to extend the setup program by writing a "C" DLL, which I've done. Pretty straightforward, and you have access to all the variables in your Wise script. So you potentially have the ability to do nearly anything that can be done from inside a DLL.
Chip H.
petermeachem
Programmer
The VB wizard does not do a good job of updating a file when it is in use. As in MFC4.. MSVCRT... . You would not believe the palaver required to copy these files in on a reboot. Quite amazing. Wise (the cheap one) does manage this trick very nicely.
However, I've just sent a VB6 programme off to a customer and now some database thing they have got does not work. I don't know if there is any connection, but it looks a bit iffy. As they know nothing whatever about the database thing, it may take a bit of time to get to the bottom of it.
However, I've just sent a VB6 programme off to a customer and now some database thing they have got does not work. I don't know if there is any connection, but it looks a bit iffy. As they know nothing whatever about the database thing, it may take a bit of time to get to the bottom of it.
My experience with InnoSetup is very good.
Try it.
Thank you,
RR.
______________________
What should not happen, will happen in the worst possible moment.
Try it.
Thank you,
RR.
______________________
What should not happen, will happen in the worst possible moment.
- Thread starter
- #27
- Status
Similar threads
- Locked
- Question