4

I have setup a local IIS instance to run and development an older ASP.NET (CLR v4.0) application that I have inherited.

I am running it an a virtual directory, and I am able to attach to the IIS process and debug it (annoying). However, I am unable to "F5" in Visual Studio to start debugging. I get an error message saying "The web server could not find the requested resource."

I have went through all of the Microsoft advice on their help page without much luck. Am I naive in thinking that this will work, or am I missing something? I even installed the IIS 6 Metabase compatibility, but that did not seem to help either.

I realize that I probably need to give more information, but I don't know what other details I need to add.

This is running on Windows 8.1 Enterprise with IIS 8, and I am using Visual Studio Professional. Thanks

1
  • I will note that the IIS logs are fairly unhelpful. However, I believe that I am seeing a 404 in the log. 2015-03-26 23:54:26 ::1 DEBUG /App/DebugAttach.aspx - 80 - ::1 - - 404 6 0 0 Commented Mar 27, 2015 at 0:00

1 Answer 1

4

MYSTERY SOLVED!!!!!!!!!

Apparently, Request filtering is installed by default. In order for debugging to work, you have to go the virtual directory -> Request filtering -> Http Verbs, and allow verb DEBUG.

Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.