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
- :
- ISAPI Settings in IIS7
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
‎Oct 28, 2010
04:50 PM
ISAPI Settings in IIS7
I was wondering if anyone knew how to do the following in an InstallScript MSI project:
1) By default when you install .NET 4.0 Framework on a 64 Bit OS (Windows 2008 R2), the aspnet_ISAPI.dll's are set to Not Allowed. How can my install set these to Allow?
2) How can I Edit the Feature settings for ISAPI restrictions to Allow unspecified ISAPI modules?
Thanks,
Greg
1) By default when you install .NET 4.0 Framework on a 64 Bit OS (Windows 2008 R2), the aspnet_ISAPI.dll's are set to Not Allowed. How can my install set these to Allow?
2) How can I Edit the Feature settings for ISAPI restrictions to Allow unspecified ISAPI modules?
Thanks,
Greg
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 01, 2010
12:07 PM
Update:
I just need to know how to do number 1.
Anyone have any ideas?
Thanks,
Greg
I just need to know how to do number 1.
Anyone have any ideas?
Thanks,
Greg
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 18, 2011
01:33 AM
You need to add a new extension under "Server Configuration\Internet Information Services\Web Service Extensions".
Call it "ASP.NET" and point it to "[WindowsFolder]Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll"
Make sure that "Allow" and "Overwrite Existing Extensions" are both set to "Yes"
This is what I do on Windows Server 2003 R2 so I guess it should work on 2008 too.
Call it "ASP.NET" and point it to "[WindowsFolder]Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll"
Make sure that "Allow" and "Overwrite Existing Extensions" are both set to "Yes"
This is what I do on Windows Server 2003 R2 so I guess it should work on 2008 too.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 18, 2011
07:48 AM
I'm working with .NET 4.0, not 2.0.
Regardless, I ended up deleting the existing extensions and creating the 2 for .NET 4.0 and added my own with the right settings and everything was fine.
Regardless, I ended up deleting the existing extensions and creating the 2 for .NET 4.0 and added my own with the right settings and everything was fine.