Visual studio stops debugging immediately. Why?

Question

0.00/5 (No votes)

See more:

VS2010

Hello everyone,

I am developing ASP.Net MVC App.

When I hit on F5 (Or clickin debug button), VS 2010 debugs and runs my app on the browser. No problem till here. However, debug stops by itself immediately(less than 1 second). So I tied to put breakpoint on Home controller, Index method. However it doesn't work as I guesssed.

While I was coding to fast I opened a window. Maybe, ı have changed some settings. However, I cant solve.

Does anyone know about this issue?

Posted 17-Mar-15 3:33am

FoxRoot

Updated 9-Jun-23 7:24am

Add a Solution

Comments

ZurdoDev 17-Mar-15 10:08am

Restart Visual Studio? Check the event viewer?

Sergey Alexandrovich Kryukov 17-Mar-15 15:28pm

Clean up project and restart studio? Remove all non-source files manually and start over?
Actually, I recently came across a .NET project which breaks the debugger, but I never faced it before. Even though the project is unacceptably bad, VS certainly had some defect. It was VS 2008 (which was one of the best VS versions), the same project with VS 2013 did not show this problem.
—SA

FoxRoot 18-Mar-15 2:22am

Thanks Sergey.
I applied both solutions (You and Ryan). Didin't solve the issue. That problem occurs only my last project. As I mentioned before, While I was typing so fast I opened CTRL + Alt + E. Maybe I have changed something. I reseted it to defaults. But nothing changed. So, it seems that, the only solution is to copy the codes and paste to new project :)

Thank you both.

FoxRoot 18-Mar-15 2:23am

Thanks Ryan. I have posted below what happened.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)