I am new to IIS world, and I was trying to see what IIS is running at my local machine. I have windows 7 and when I go to help->about of IIS manager, a pop up shows up, whose second line says "Version 6.1 (Build 7601: Service Pack 1)", so I thought this is version 6.1 of IIS. However right at the end of same Pop up I can see another line "Internet Information Services(Version 7.4.7600.16385)".
now I am confused which IIS version I am running 6.1 or 7.5?
I have done bit of research and found out that IIS version 7.5 belongs to Windows7. Can I safely assume that if I have windows7 I can not have IIS version other than 7.5?
Is there any good tutorial/ reading material online to understand IIS and how it works?
IIS is tied to the operating system.
This is a little old post, but just thought I'd share. Here it is in a book!
Section: IIS 8.0 Requirements - in the Second Sentence of that section.
Update in response to Himanshu Singh's answer, because I can't comment: I wanted to talk about 'upgrading' and to IIS 8.0 Express. I am specifically interested in IIS 8.0 because of websockets, IIS 8.0 Express doesn't support websockets, so it isn't a 'true upgrade'. I dont know what features it supports from 8.0, because I stopped reading about it after learning it doesnt support the websockets protocol.
Here where I found information about IIS 8.0 Express not supporting websockets.
Websocket issue with IIS 8 Express on Windows 7
Also, to answer the question directly, yes you can 'safely' assume your version of IIS is 7.5
You can definitely install other version of IIS on Win7. Like IIS Express 8.0 will run on Windows Vista with SP1 and all later versions of Windows.
To study IIS online you can definitely go to http://www.iis.net/
Related
Plain and simple: Is it even possible for a SignalR Application to run off IIS 8.5 on Windows Server 2012 R2, or is this not a compatible setup? There are tons of threads all over Stack Overflow that pose the same issue, that the dynamically generated script located at signalr/hubs is 404ing, but the threads with solutions are not using my iis/server setup.
I tried following the tutorial at https://learn.microsoft.com/en-us/aspnet/signalr/overview/getting-started/tutorial-getting-started-with-signalr but it seems that it only works in Visual Studio's IIS Express. As soon as I move the application to our server, I get the error everyone else on SO is getting.
Here's the supported platforms for Signalr on the official documentation:
https://learn.microsoft.com/en-us/aspnet/signalr/overview/getting-started/supported-platforms
It stops short of Windows Server 2012 R2, but the documentation is dated. Any advice is appreciated.
Yes, Windows Server 2012 R2 and Windows Server 2016 both support SignalR. Just ensure WebSocket support is enabled and you're all set.
IIS Express is a cut-down version of IIS (which frustratingly does not work with IIS Manager), but internally it uses the same execution engine (including HTTP.sys integration) so it uses the same web.config files as the full-fat IIS too, so it supports SignalR too.
("IIS Express" is a thing because previously VS shipped with a simple web-server called Cassini, which used ASP.NET System.Web.dll for everything, which worked for simple applications but for more complex applications there was sufficient differing behaviour that it made development difficult)
This only references requirements for clients:
http://msdn.microsoft.com/en-us/library/8z6watww%28v=VS.100%29.aspx
I am looking for similar documentation in reference not just for .NET 4, but ASP.NET 4 and what IIS versions, OS SP's, etc. are required. I would like to see if there are any pitfalls to requesting IT to install ASP.NET 4 and MVC 3 on our server. Don't want to have egg on my face :)
Per the documentaiton on the installer download for .NET 4.0 ( http://www.microsoft.com/download/en/details.aspx?id=17851)
Additional Requirements for Server
Installation
If you have to perform a server
installation, your computer must have
the following software in addition to
the basic requirements:
•Internet Information Services (IIS)
version 6.0 or later. To access the
features of ASP.NET, IIS with the
latest security updates must be
installed before the .NET Framework is
installed. ASP.NET is supported only
on Windows XP Professional, Windows
Server 2003, Windows Server 2008, and
Windows Server 2008 R2.
So it will run in IIS 6.0 or above. If you want to know which operating systems support asp.net 4.0, that would be any operating system that supports IIS version 6.0 or above. This jives with my comment on your question.
That said, the biggest thing to watch out for is that you have to configure any .NET 4.0 IIS application to use a different applicaiton pool than 2.0, 3.0, or 3.5. There's more info on this here: http://johan.driessen.se/posts/getting-an-asp.net-4-application-to-work-on-iis6
WinXP has IIS 5 and the .net framework and ASP.NET 4 is supported on it. For server technologies, IIS6 and newer are supported, as Server 2003 which has IIS6 is the oldest server technology that supports ASP.NET 4.
I am working on migrating more than 20 websites from IIS 6.0 to Windows 2008 server/IIS 7.0. All these websites have their own IIS configurations and settings. Wanted to know, if there is any way by which I can read my IIS 6.0 configurations for each and every website and set the same/equivalent configurations on IIS 7.0?
I want to avoid using manual compare and paste stuff over here.
I finally did this using the Web deploy Tool.
Thanks everybody
Moving some old sites off an old server to a newer one running Windows Server 2008 x64. Some of the sites are running ASP.NET 1.1. I've gotten them all to work with minimal hiccups (other than making sure to remap each ASP.NET version via aspnet_regiis and copying over the 1.1 machine.config to the Framework64 location) except for FormsAuthentication doesn't appear to be supported for ASP.NET 1.1/IIS7/7.5. Meaning, FormsAuthentication is not an option in IIS Admin, and FormsAuthentication settings in config files merely causes 403 Not Authorized page to render instead of redirecting to a login page etc.
Has anyone gotten it to work? I really just want it quick and dirty as it's only affecting three sites and this is the only remaining issue. I'd prefer not to have to keep a Win2003 server around (virtual or otherwise).
Thanks.
OK First of all I think there is a difference between IIS7.0 and IIS7.5 in that 7.0 seems to be more compatible with ASP.NET 1.1.
You should be able to install IIS7.0 on Windows 2008 server but I don't think it is available on Windows 7. Please not that .NET 1.1 should be running under the WoW64 configuration since I don't think it supports 64bit natively. Look at this article for installing ASP.NET 1.1 on Windows 2008 with IIS 7.0 - http://learn.iis.net/page.aspx/472/how-to-install-aspnet-11-with-iis7-on-vista-and-windows-2008/
I came across this article for upgrading ASP.NET 1.1 to IIS7.0 - http://learn.iis.net/page.aspx/270/upgrading-aspnet-11-to-iis7-on-windows-vista--windows-server-2008/ which might be helpful. Especially look at the section on "Differences between Integrated Mode and Classic Mode" where forms authentication behavior differences are discussed.
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