As of recently there is a express edition of the IIS 7. It is bundled with this crazy new tool Web Matrix (http://www.asp.net/webmatrix).
A real IIS instead of the development server in Visual Studio would have many advantages.
Does anybody know, if this IIS edition can be separately downloaded ?
Can it be installed on Windows XP (Professional) ? If yes, are there conflicts with the old IIS 5.1 on XP ?
Can it be integrated in Visual Studio (2008, 2010)?
It will be released for download separately to the WebMatrix but as of yet it is only available as part of the WebMatrix bundle
It can be used on XP SP3, it will not conflict with 5.1 as it runs as a self contained instance
Yes, it can be integrated with VS2010 (you can tell VS to use IIS7 Express rather than Cassini)
Some useful links -
ScottGu addresses your first question and part of the integration work
The IIS7 Express FAQ where your supported platform questions are answered (along with a whole lot more)
Related
Some while ago I've upgraded an asp.net 1.1 application (which ran on IIS 5 and 6) to .net 3.5 and later to .net 4.0 (and IIS 7.5)
Still, when I want to open it in VS, I need to install the "IIS Metabase and IIS 6 Configuration Compatibility". It works after I install it, but..
How to get rid of this requirement?
When debugging ASP.NET projects using Windows 7's IIS7.5 web server, Visual Studio 2010 RTM requires the IIS6 Metabase and IIS6 Configuration Compatibility components.
However Visual Studio 2010 SP1 fixes this dependency and VS2010 now works natively with IIS7.5 without any need to use the IIS6 bits.
I also proved this by knocking out a test project in Visual Studio 2003 and then copying to two different IIS7.5 machines configured as:
PC1: VS2010 RTM, no IIS6 Compatibility
PC2: VS2010 SP1, no IIS6 Compatibility
Here's a long-winded explanation (in case you need it) but the short answer (which also appears there) is to run
aspnet_regiis -ga <WindowsUserAccount>
I believe that this only happens when you upgrade a machine or you are not an administrator of the machine when you install .Net/Visual Studio. I recently had to do this on a brand new laptop with Visual Studio 2010 installed by others before I had admin rights. So, the way to get rid of this requirement from your end is to do the install as an admin.
I've inherited a ASP.NET 1.1 webapp that runs in production on win2k3 under IIS6. I'd like to closely match this environment during development and testing. For reasons I won't go into, using Cassini/VS Development Server isn't ideal so I'm trying to set up my Visual Studio environment to use IIS6. I do my development on VS 2008 on Win7, and from what I can tell, IIS6 is only supported on Win2k3 and XP Pro x64. Am I stuck using Win7's built-in IIS7?
You will have to use IIS7 but if it is run in classic mode then it will closely emulate the IIS6 way of working. For the differences I wouldn't bother with the overhead of a VM, there aren't enough incompatibilities that I know of to warrant it.
I am planning to buy a new laptop to learn asp.net web applications and also windows applications. Do we get IIS7 installed when we buy the home edition of windows 7 or should we buy windows 7 professional version?
Looking at some documentation on TechNet, it looks like all the Windows 7 Home editions (Starter, Basic, Premium) have the ability to install IIS, but it is not installed by default.
If you just want to learn, Visual Studio has a built in webserver for development that will work. If you want to deploy your web applications, this page has information on which versions of Windows 7 have which IIS options available
Following this thread, no problem found so far.
You don't need IIS for ASP.NET Development if you use Visual Studio.
Visual Studio Express for the web is free, and comes with its own web server.
http://www.microsoft.com/express/Web/
You can also create windows programs with Visual Studio Express for windows.
http://www.microsoft.com/express/Windows/
If you want to do both, then you may need to buy Visual Studio.
If you want to do local debugging of asp.net using IIS then you need one of these versions. Not supported on Windows 7 Home.
Windows 7 Ultimate
Windows 7 Professional
Windows 7 Enterprise
reference:
http://msdn.microsoft.com/en-us/library/kd3se23d.aspx
I want to setup a Win7 virtual machine to develop using Visual Studio 2008 and ASP.Net 3.5.
I don't know what the best order to install what I need. I will need to install:
a) Visual Studio 2008
b) IIS
c) Service Packs for Visual Studio and/or .Net Framework
My last try was bad, I cannot do my old ASP.Net 3.5 web app to work on Win7 (works fine on Win2003).
Another questions are, if I choose to use Visual Studio 2010 (to develop ASP.Net 3.5), it's recommended? And the installation order will change?
Thanks for all
Your best bet is to actually use the Microsoft Web Platform Installer. This tool will walk you through installing ALL of the components you need to host a web application. Pick your platform (PHP, ASP.NET, etc), an optional application (DasBlog, etc), and even choose to download Visual Studio 2008 Web Developer + SQL Express. It will install everything for you seamlessly. I've used it and I highly recommend it for a "clean" install.
I'd install IIS first, then Visual Studio 2008. The framework will come with VS.NET 2008. If all goes wrong learn to use aspnet_regiis.exe
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