I've blogged quite a bit about using Visual Studio to develop and debug IIS 7.0 applications in the past. A few weeks back, I put together a detailed article about using Visual Studio 2008 to work with IIS 7.0 applications, collecting all the various how-to and gotchas in one place.
Now, you can find the same information for Visual Studio 2005, in a new article titled Using Visual Studio 2005 with IIS 7.0.
The article talks about:
– Installing necessary IIS 7.0 components on your Windows Vista or Windows Server 2008 server to be used with Visual Studio 2005.
– Using the different Visual Studio web application project models with IIS 7.0 applications
– Connecting to remote IIS 7.0 applications
– Debugging local and remote IIS 7.0 applications
Visual Studio 2008 fixes a number of issues that affect Visual Studio when working with IIS 7.0, making it easier to go about your work. You can find the same level of detail on using VS 2008 in my other article, Using Visual Studio 2008 with IIS 7.0.
Just for reference, here are some of the Visual Studio related posts I've done in the past that are all included (to various degrees) in the article:
Using Visual Studio 2005 with IIS 7.0
Using Visual Studio 2008 with IIS 7.0
Debugging IIS 7.0 Web applications remotely with Visual Studio 2008
Fix problems with Visual Studio F5 debugging of ASP.NET applications on IIS7 Vista
As always, if you hit any issues, let me know by leaving a comment.
Thanks,
Mike
.
A few weeks back, I put together a detailed article about using Visual Studio 2008 to work with IIS 7
I went through all your listed steps to get VS2005 to debug on IIS7/Vista and was successful with normal ASP.NET web applications but NOT with applications using the AJAX extensions.
I tried what some other users recommended and switched IIS to use the classic app pool, but still got the error.
I am running Vista Home Premium using VS2005 SP1 and the Vista VS2005 SP1 update and I also have installed your hotfix for eliminating the need for Windows Authentication. Yet I still can't overcome this AJAX error. If I remove the AJAX specific content from the web.config it will work, but I need to use AJAX for my project.
Any ideas?
OK, I wiped my hard drive and installed Vista Ultimate, hoping this would let me get around the problem listed in my comment above. But I’m still getting an error.
Quite simply, this seems to be a MAJOR problem with IIS 7! How can Vista not support debugging VS2005 projects WITH AJAX using IIS 7?
The specific error message is quite basic:
“Error: The web server is not configured correctly”
I have Windows authentication enabled, running as administrator, and tried switching to the classic application pool. Still no luck.
PLEASE! Any help, otherwise I have to go back to using WinXP and IIS 6.
Thanks,
Chris
I had other issues with Vista SP1, VS 2005 and IIS 7 and I have written a post here http://developershelf.blogspot.com/2008/05/problem-loading-iis7-hosted-wap.html
I`ve read a number of programming articles and and they discourage programmers to use vb. i am quite concerned because I am a programming student and at my university we use vb as our programming language.
I`ve read a number of programming articles and and they discourage programmers to use vb. i am quite concerned because I am a programming student and at my university we use vb as our programming language.
The “Using Visual Studio 2005 with IIS 7.0” does not appear to be 100% accurate.
Step 4 in the section titled “Connect to an IIS 7.0 Web Site Using Front Page Server Extensions” details the use of the command line -u
“%CommonProgramFiles%Microsoft SharedWeb Server Extensions50binowsadm.exe” -o install -p LM/W3SVC/
but there are problems with this command line.
First, I have no clue as to what a SITEID is or how it is determined.
Second, CommonProgramFiles is only accurate for a 32 bit installation. CommonProgramFiles(x86) is used for a 64 bit install.
Third, the -p LM/W3SVC/ portion is unlikely to be accurate. All the examples shown in the help on the owsadm command show the usage as -p 80 suggesting that the -p argument specifies the port.
I cannot be certain of the third problem until I get past the first one.