This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Dynamic URL for Install From The Web
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
‎Aug 03, 2007
10:01 AM
Dynamic URL for Install From The Web
Hello,
My Basic MSI project build an Install From The Web installer.
in the release, I can give the url where the files are located in the URL for your files section of the Internet pane.
Ok, it works but it do not allows to manage a kind of miror between two http servers.
I would like to have a dialog that give me the choice between two http (like the language dialog) and dynamically redirect the download accordingly.
I don't have any idea on the way to deal with that.
At this time, I have to manage two distinct releases : one for the first http site and one for the second... not really smart.
Thanks in advance for any help provided.
Pascal
My Basic MSI project build an Install From The Web installer.
in the release, I can give the url where the files are located in the URL for your files section of the Internet pane.
Ok, it works but it do not allows to manage a kind of miror between two http servers.
I would like to have a dialog that give me the choice between two http (like the language dialog) and dynamically redirect the download accordingly.
I don't have any idea on the way to deal with that.
At this time, I have to manage two distinct releases : one for the first http site and one for the second... not really smart.
Thanks in advance for any help provided.
Pascal
(4) Replies
‎Aug 03, 2007
04:45 PM
I don't think there's anything built in; I believe you can use the /um switch to setup.exe to specify the location (URL) of the MSI database for a Web release (it's documented that way for a Downloader build, anyway), so that might be one way to manage...
To have something built in, you (meaning "everyone") can vote for this as a feature request at www.installshield.com/feedback.
To have something built in, you (meaning "everyone") can vote for this as a feature request at www.installshield.com/feedback.
‎May 02, 2008
12:31 PM
Hi,
We have an InstallScript One-click install (actually developed in IS12 but applies here) that we give to our resellers. They edit the bootstrap.htm & setup.htm files to point to their own web server files, from which their own customers install. I have converted that One-Click installer to Basic MSI. I am testing on my own PC and can only get it to work if I hard-code my local webserver directory http://localhost/myapp in the "URL for your files" property. Can I leave the "URL for your files" property blank and edit the install.htm files created so they point to http://localhost/myapp?
I have several posts on this MSI One-Click install (in the IS12 forum) and opened incidents and still have not found any solutions. Please help!
Thanks,
-Jeff
We have an InstallScript One-click install (actually developed in IS12 but applies here) that we give to our resellers. They edit the bootstrap.htm & setup.htm files to point to their own web server files, from which their own customers install. I have converted that One-Click installer to Basic MSI. I am testing on my own PC and can only get it to work if I hard-code my local webserver directory http://localhost/myapp in the "URL for your files" property. Can I leave the "URL for your files" property blank and edit the install.htm files created so they point to http://localhost/myapp?
I have several posts on this MSI One-Click install (in the IS12 forum) and opened incidents and still have not found any solutions. Please help!
Thanks,
-Jeff
‎May 14, 2008
09:56 AM
Thanks to Tech Support for their help. The solution to my "Hard-coded URL" issue is to set your release's Web Type property to One Executable. It creates a single setup.cab and separate htm files.
-Jeff
-Jeff