I downloaded IBuySpy Store VS VB on to my computer. I got the store database and VS project components. Every thing looks OK, except the following message pops up when I start the project:

Error while trying to run project: Unable to start debugging on the web server. The project is not configured to be debugged.

What causes the above error? What can I do to fix it?

The project runs just fine without error if I start it without debugging.

Thanks for any help.

Add the following line:



To the node in the Web.config.

good luck!

same problem here .. I have tried everything in the newsgroups... even changing some process setting to system. I disabled my McAfee firewall... only thing I can see that someone said is my linksys router may not let the Debug verb through. Is this for real.

xp pro ... everything works fine otherwise... I can attach to the wp process... have not figured out where to set a breakpoint to test yet.. but would like to not have to manually attach.

I did what pohare2 said and fixed the problem.
Thanks.

Hello,

I had a similar problem. I did the following:

STEP 1
- In the web.config file, I added <compilation debug="true" /> under the <system.web> node as suggested by pohare2.
- However, I then get the following error when I hit F5 (Start):
-- This is what appears in a message box: "Error while trying to run the project: Unable to start debugging on the web server. There is no managed code running in the process. In order to attach to a process with the .NET debugger, managed code must be running in the process before attaching."
-- This is the message in the Output window: "Auto-attach to process '[516] aspnet_wp.exe' on machine '<MACHINE-NAME>' failed. Error code 0x8004000e."

STEP 2
- To solve the above error message, I found the way to manually attach to the aspnet_wp.exe process. You have to hit CTRL+F5 (Start without debugging). This will open the default page in IE without the debugging. Then go to Debug/Processes in the IDE and select aspnet_wp.exe and click Attach button. This method is mentioned in the .NET Framework Help.
- Ok, so doing that showed the Debug Pause and Stop buttons in the .NET IDE.
- Now, I add a breakpoint in the Registration page at the btnRegistor_Click event. In the IE window that is already opened by CTRL+F5, I go to the registration page, hit the Register button and it does not stop at the breakpoint.
- Closing IE window (that initially opened through CTRL+F5) does not stop the code execution. You have to hit the Stop button yourself.

Can anyone tell me:
1) How I can step through the entire code?
2) Why should I have to manually attach aspnet_wp.exe?
3) Why will .NET not do it on it's own? Or rather, what can I do to make it attach on it's own and simply hit F5 to run the project and be able to step through it?

I have another much bigger ASP.NET project running on my desktop (a different machine than this) that I downloaded from our VSS Server and didn't have any of these issues. I can step through the entire code and I do not have to do any manual attaching. I will look at the web.config file and project properties for it tomorrow. I hope I can figure this out but please advise me on this.

Thanks in advance for your help.

This may help: http://www.gotdotnet.com/team/csharp/learn/whitepapers/howtosolvedebuggerproblems.doc

Thanks for sending that link shedao. I looked at the web.config files on my desktop machine too and from the debugging standpoint, there is no difference. Also, IIS on both the machines are set up in a similar fashion.

I am still unable to get rid of having to manually attach the aspnet_wp.exe process. I hop I can find a solution soon. I am a newbie at this stuff.

Thanks.

Hello, I too was getting the same error as above.  However, I was able to resolve it by stopping restarting the Machine Debug Manager service.

Hi,

Had the same problem. Stopping and Restarting the MDM (WebWalker's advice) solved my problem.

Ger.

if you have a .NET 1.1 web app and try to build and run in debug mode against .NET 2.0 in visual studio 2003 you will get this too.

 Set the virtual directory to use 1.1 in iis to resolve this problem.

another thing to try is running an iisreset ... Start  > Run > iisreset or kill the aspnet_wp worker process.

 

 

Hello all,I had the same problem and none of the above fixed it. I'm running 2 frameworks 2.0 and 1.1. I had to do the following to switch to 1.1.In a dos prompt do the following:
cd c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
aspnet_regiis.exe -u
cd c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
aspnet_regiis.exe -i

Hope that helps someone. I have to do the opposite to go back to 2.0. I created bat files to do it. Kind of painful but it worked.

 

Excellent Excellent Excellent, I fix my problem. Thanks.

 

Excellent Excellent Excellent, I fixed my problem. Thanks.

Excellent, I fix my problem. Thanks

dymcgee:

Hello all,I had the same problem and none of the above fixed it. I'm running 2 frameworks 2.0 and 1.1. I had to do the following to switch to 1.1.In a dos prompt do the following:
cd c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
aspnet_regiis.exe -u
cd c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
aspnet_regiis.exe -i

 Yep. That did it for me too. Great idea with the batch files - thanks!! :)