I have had many requests come in to a project that I work on, to include an IIS 7 module interface.
Does anybody know of any resources for creating an IIS 7.0 module interface?
I have searched http://www.iis.net and I have not really found a good article on the basics of how to create an IIS 7.0 module interface.
It can be for any programing article on how to create a module interface for IIS 7.0 (Windows 2008) or IIS 7.5 (Windows 2008 R2).
I found a couple sources, has anybody found anything that is better or more descriptive on the programming side?
Modules Overview
This may help to get started:
http://learn.iis.net/page.aspx/121/iis-7-modules-overview/#Getting
http://www.iis.net/ConfigReference/system.webServer/globalModules
Scroll down to "Step 3 - Creating the Image Copyright UI Module" of this article:
http://learn.iis.net/page.aspx/168/an-end-to-end-extensibility-example-for-iis-70-developers/
It provides a step-by-step on creating a GUI for configuring a custom IIS 7 module.
Related
I hate to ask a question that seems like it should be easy to find the answer to on the web, however I am unable to find a straightforward answer anywhere as to how to check what version of ASP.NET is installed on my Windows Server 2008 r2. Any help with this would be much appreciated. Kind regards, Jon
Read registry key, HKEY_LOCAL_MACHINE\Software\Microsoft\InetStp\Components\ as documented in
https://learn.microsoft.com/en-us/iis/install/installing-iis-7/discover-installed-components
As you use IIS 7, its "ASP.NET" feature matches ASP.NET 3.5 you are looking for. If you want to check ASP.NET 4.x, then this approach won't work.
Generally speaking, the ASP.NET component in IIS wraps over aspnet_regiis command line tool to register ASP.NET bits on IIS (ISAPI and so on). Microsoft designed it this way so it felt more natural. However, it turns out to be a disaster later, as .NET Framework new releases can easily break the design.
For example, on IIS 7 if you use ASP.NET 4.x then you have to manually run aspnet_regiis from .NET Framework 4.x installation folder, as there is not ASP.NET 4.x component on IIS 7.
You can go to
C:\windows\Microsoft.NET\Framework
and check if there is v3.5 folder
I'm uing various different versions of WIX trying to get an installer to be able to install to both IIS versions. I've heard that WIX doesn't natively support IIS7 so one must make a CA to provide the functionality
Does anyone have an example of how to create functionality which can do this? I've already got an installer to install the web site to IIS6 but can't attach this with an IIS7 custom action I've found.
Edit: Ahh okay I'll rephrase my question.
How would I create a UI to allow a user to choose the web site to use for IIS6 and IIS7 (i.e support all versions of IIS to query)?
WiX 3.5 supports IIS7. You should use the same elements of IIsExtension you normally do for IIS6. Besides, "IIS6 compatibility" prerequisite is not required any longer.
I have an application that I am wrapping up in an installer. I would like to, either through the registry, or by writing a script, enable IIS 6 metabase compatibility in IIS 7.
Does anyone know if this is possible?
You should be able to use dism.exe or pkgmgr.exe or ocsetup.exe to automate the installation of this component. You can technically do this these days because Windows Vista ( as far as I know ) always caches the WIM file needed to install the component.
Still, I wouldn't do it. I'd just upgrade to InstallShield 2010 which has native II7 capabilities. Or you could use Windows Installer XML 3.5 which has the same. You eliminate the dependency and simplify the deployment in the process.
If you decide to do it anyways, check out this good article:
Install Typical IIS Workloads
UI Name Update Name
IIS 6 Metabase Compatibility
IIS-Metabase
IIS 6 WMI Compatibility
IIS-WMICompatibility IIS 6
Scripting Tools IIS-LegacyScripts
I just got application written in ASP.NET and VB, can i deploy it on any IIS?
Are there any files in project with that kind of information?
There are no files or magic numbers anywhere that can tell you this. Chances are preety good that it will run on a newer versions of IIS but even then your goign to need to know what functionality it requires. For example is it using WebDav? IIS is preety good at being backwards compatible but forward compability not so good. For example IIS7 introduced new functionality which if the application is using it, would prevent it from running on IIS6.
Do you know what version of .net it requires that is more likely to bite you then anything else?
Any IIS that supports ISAPI, I guess, but IIS 5.1 + is recommended (.NET probably won't run on OS that run IIS4 anyway).
Here is a good MSDN link detailing which IIS version comes with which version of Windows as well as useful links for configuring it.
ASP.NET and IIS Configuration
IIS 6 is the minimum for recent .NET versions (i.e. Windows 2003) because Win2000 is not supported (considering server only here).
The Windows version will tell you the IIS version:
Server 2003: IIS 6
Server 2008: IIS 7
Server 2008 R2: IIS 7.5
Also XP: IIS5.1; Vista: IIS7
Are there any issues with running an asp.net 1.1 application under windows server 2008 64-bit web edition?
I have never tried it myself, but I did find the following pages that you might find interesting:
This blog has an in depth walk through of configuring ASP.NET 1.1 on Windows Server 2008. The author does not say if it is x86 or x64, so I would just assume its x86. But either way, it looks like the author had to jump through some hoops to get the ISAPI filter setup correctly.
I also found this thread on the IIS7 forums where someone discuses having poor performance from ASP.NET 1.1. on x64 Win2k8. So from poor performance I would assume it worked to some extent. Unfortunately towards the end of the thread the author mentions encounter 500 errors, and then the discuss stops :-(
So from what I've read I would guess that its possible, but I would also guess that you would have less hassle if you could find some alternative that didn't involve both II7 and x64.
I have recently been testing our application on 64 bit 2008. Our application is .net framework 3.5 but we had a few problems.
The main issue we had was with 3rd party components such as Aspose words which were not built for 64 bit and caused an error. Unfortunatly you wont know without trying it..
.NET 1.1 is 32 bit only hence the app pool would have to run as 32 bit and use the classic pipeline. I haven't tried myself and I would do all that I can to not have to install .NET 1.1 on a 2008 server but it should work.
No problem. Just follow intructions on
http://learn.iis.net/page.aspx/472/how-to-install-aspnet-11-with-iis7-on-vista-and-windows-2008/
The option "CGI Restrictions" (last step) is found on IIS7 admin by clicking on the machine name.
I'm pretty sure that the article at http://learn.iis.net/page.aspx/472/how-to-install-aspnet-11-with-iis7-on-vista-and-windows-2008/ is for NON-R2 versions of Windows Server.
As far as I know ASP.NET 1.1 cannot run (or at least, not run well) on Windows.
There are some band-aid solutions around that various people have posted / blogged but this isn't supported by Microsoft.