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
- :
- Setting IIS virtual dir property depending on feature selection
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
‎Sep 13, 2007
07:19 AM
Setting IIS virtual dir property depending on feature selection
Hi
I'm building a simple MSI file setup where I need to enable/disable anonymous authentication in a virtual directory depending on which feature is installed. The virtual directory does not exist from before.
I thought this would be possible by adding the IIS virtual dir in two features, one for each configuration setting, where only one would be installed, but that doesn't seem to be possible. Whenever I try to add the site twice I get the message: "The alias you have given, Server, is not unique"
Does anyone have any ideas on how I can solve this?
I'm building a simple MSI file setup where I need to enable/disable anonymous authentication in a virtual directory depending on which feature is installed. The virtual directory does not exist from before.
I thought this would be possible by adding the IIS virtual dir in two features, one for each configuration setting, where only one would be installed, but that doesn't seem to be possible. Whenever I try to add the site twice I get the message: "The alias you have given, Server, is not unique"
Does anyone have any ideas on how I can solve this?
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 09, 2008
07:42 AM
Hi
still noone that has any idea about this?
Everything seems to work if the web site I install to is set to .Net 2.0 before the installation, but that is rarely the case with our customers, and in many cases it can not be done either due to customer demands.
still noone that has any idea about this?
Everything seems to work if the web site I install to is set to .Net 2.0 before the installation, but that is rarely the case with our customers, and in many cases it can not be done either due to customer demands.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 16, 2008
03:34 PM
I'm more or less having the same issue. Ever get it resolved?
Jesse
Jesse
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 17, 2008
02:20 AM
No, I just got the workaround as I mentioned in the previous post