Posted 28 September 2004 - 23:44
Quick and dirty answer:I have succeeded in doing this by modifying the setup.exe with
setupini.exe after it is built.
This is probably easier when deploying to a website than seperately building a release for each site, especially if you cannot know the site name until deploy of after building the release.
To find what needs to change, check the release target directory while the release is building. Setup.ini is built relatively soon in the build, and present until just before the release is complete. Copy this file to another location so that you can read it at your leasure.
In my setup.ini there was the following section:
QUOTE |
[Harmony.msi] Type=3 Location=http://78zch16w2k/installs/webinstall/Harmony.msi |
(obviously a test location)
So all that I had to do when I moved the build was to run setupini.exe:
this changed the location for the release from webinstall to webinstall2.
To verify my changes, I cleared out my Internet Temporary Files, put the install release into webinstall2, and just the setup.exe in webinstall. I then launched the setup.exe from webinstall.
Implications for this are not huge. Since you need to have setupini.exe, it is not practical to do this on the users target device. Changing the Location property from the command line woule be much more desireable. On the other hand, it is probably easier to implement setupini.exe into a website deployment process than to implement an entire release build.
Edited by MonkeyK, 30 September 2004 - 13:53.