Hi,
I have some newb questions on the possible benefits of using NSIS. Is it possible to be able to use the same installer to install the package multiple times on the same machine? For example, our developers are using the visual studio built-in installers to give us a different msi package with a different guid for each instance of web code that we need to be installed on the same server. So for example if we had 3 sites running on the same web server, I would have to have 3 different msi packages. This is a pain for the devs and a pain for me. The developers are getting tired of cutting these extra builds for each release and want us to just install the package in a temp directory, then manually copy the web code to the directory that we want it installed in.
To add on to the same question, when I have all three installed, if I go to add / remove programs to upgrade the site, I now have "Web Code release XX Live_1", "Web Code release XX Live_2", "Web Code release XX Live_3". As you can tell, its difficult to figure out what web code goes to which site. Is it possible to prompt the user during installation to ask for a name to put into add/remove programs. So instead of seeing "Web Code release XX Live_1", I could have "Web Code release XX Live_CUSTOMERNAME".
I appreciate everyones help.
Thanks
Newb Question: Multiple installs on same server
3 posts
Yes, you can use information both from the machine where the setup was compiled and information from the machine the setup is running on in the name and install path if you desire. You could also allow the user to specify it on the command line.
Can this not be done with MSI? I thought you could update some of the variables in the database before you hit a certain point in the UI.
Can this not be done with MSI? I thought you could update some of the variables in the database before you hit a certain point in the UI.
Hi,
Thanks for responding. The devs have told us in the past that a lot of functionality of the installers are limited due to they are using the built in visual studio 2010 installers.
Thanks
Thanks for responding. The devs have told us in the past that a lot of functionality of the installers are limited due to they are using the built in visual studio 2010 installers.
Thanks