|
|
|
|
#1 |
|
Junior Member
Join Date: Sep 2010
Posts: 4
|
Should be simple, but...
I am pretty much clueless when it comes to scripting.
Here is what I am trying to do: I have 5 different software installations of different products that I am trying to condense into a single installer package to increase user-friendliness of the installation. Most of them are just single .exe or .msi files, but a couple have more files involved. All I really need to do is wrap all of these packages up into an exe file, and when the end user runs it, have it copy these installation files into a temporary folder on their machine and run a batch file that will install all of them one after another. Not sure if NSIS is what I need to be able to do this. Anybody have any suggestions? Thanks so much! |
|
|
|
|
|
#2 |
|
Major Dude
Join Date: Jun 2001
Posts: 1,173
|
read the documentation - everything is in there.. just to give you a very basic skeleton to work with:
PHP Code:
|
|
|
|
|
|
#3 |
|
Senior Member
Join Date: Nov 2005
Posts: 115
|
I'd use $PLUGINSDIR instead, that way the installer doesn't leave files.
|
|
|
|
|
|
#4 |
|
Major Dude
Join Date: Jun 2001
Posts: 1,173
|
can do that (call InitPluginsDir first) - the reason I stick third party installers in TEMP is that in the past, some of them allow a user to only install some features.. then the user goes to use the application, hits some feature almost immediately that needs an additional install, and the original app can't find the installer anymore (I think all of the MSI ones now copy the package to the windows installers store thing, so not an issue for those so much). Placed in $TEMP, it'll be available until the user (or some utility) clears out temporary files.
Depends on one's needs, really
|
|
|
|
|
|
#5 |
|
Junior Member
Join Date: Sep 2010
Posts: 4
|
Thanks so much for all of the help, everyone!!
|
|
|
|
![]() |
|
|||||||
| Thread Tools | Search this Thread |
| Display Modes | |
|
|