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
- :
- Post IIS installation of a service on D drive
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 23, 2008
05:03 AM
Post IIS installation of a service on D drive
We use installshield to install a .net IIS service and as part of the installation Installshield triggers the installation of IIS if it is not on the computer already.
The problem we encounter is that when install shield triggers the installation of IIS the subsequent installation of our service is done on the D drive not to the wwwroot directory. Is there a way of getting Installshield to install it in the correct directory? The result of this is that we need to manually set up the directory where the service was installed as a virtual directory in wwwroot which as you can imagine is not desirable.
If we manually install IIS before starting our installer there is no problem Installshield installs our service correctly. We presume that Installshield is reading the registry before and not after the installation of IIS for the for the PathWWWRoot and is defaulting to D:/ when it is not found but obviously we do not know this for sure.
Any ideas would be very helpful.
Regards,
Daryl
The problem we encounter is that when install shield triggers the installation of IIS the subsequent installation of our service is done on the D drive not to the wwwroot directory. Is there a way of getting Installshield to install it in the correct directory? The result of this is that we need to manually set up the directory where the service was installed as a virtual directory in wwwroot which as you can imagine is not desirable.
If we manually install IIS before starting our installer there is no problem Installshield installs our service correctly. We presume that Installshield is reading the registry before and not after the installation of IIS for the for the PathWWWRoot and is defaulting to D:/ when it is not found but obviously we do not know this for sure.
Any ideas would be very helpful.
Regards,
Daryl
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 23, 2008
10:20 AM
It would seem that it is the IISROOTFOLDER that is being read when IS starts (at which point it does not exist) and is being set by the Windows Component Installer when it installs IIS.
If we were able to force a re-read of the variables after IS triggerd the IIS install it would resolve the problem for us, we think, but we do not know how to do so.
Any ideas?
If we were able to force a re-read of the variables after IS triggerd the IIS install it would resolve the problem for us, we think, but we do not know how to do so.
Any ideas?
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)