VS.NET Hangs on F5(Debug)

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

My debugging capabilities within Visual Studio 2003 have stopped working.
None of my applications created over the past year will run in debug (F5)
mode. I created a simple "Hello World" application and it will not run in
debug mode either.

My applications run successfully using Skip Debug (Ctrl-F5) or when being
launched from Windows Explorer.

I attempted to repair the install, but the install hangs at "Generating
Setup Script". I have also tried uninstalling, but the uninstall hangs also.
I have re-booted and tried this a number of times. I have verified the user
settings for my login and SQLDebugger.

Does anyone know what the cause of my problem might be?
Has anyone had this problem repairing the intall or running the uninstall?
If so, how did you resolve this issue?

I appreciate any help you can provide!

Thank you,
Philip
 
Philip said:
My debugging capabilities within Visual Studio 2003 have stopped working.
None of my applications created over the past year will run in debug (F5)
mode. I created a simple "Hello World" application and it will not run in
debug mode either.

My applications run successfully using Skip Debug (Ctrl-F5) or when being
launched from Windows Explorer.

I attempted to repair the install, but the install hangs at "Generating
Setup Script". I have also tried uninstalling, but the uninstall hangs also.
I have re-booted and tried this a number of times. I have verified the user
settings for my login and SQLDebugger.

Does anyone know what the cause of my problem might be?
Has anyone had this problem repairing the intall or running the uninstall?
If so, how did you resolve this issue?

I appreciate any help you can provide!

Thank you,
Philip
Click to expand...

I'm not sure this is your problem but it's worth a try :

http://groups.google.be/groups?hl=n...vs.net&ie=UTF-8&as_uauthors=phoenix&lr=&hl=nl

Yves
 
MS Support helped me solve my problem. It turns out that the culprit was
most likely N Internet Security. Even though I had been running MS Visual
Studio .NET 2003 successfully along with N Internet Security, an update may
have caused this or I may have "blocked" something inadvertently.

Anyway, once I uninstalled N Antivirus and Internet Security, and
reinstalled Visual Studio .NET (using vacmus), my problem went away.
Microsoft support was very helpful and spent quite a bit of time explaining
to me how to prevent this issue in the future.

For more information, see Microsoft Knowledge Base Article - 250670.

Thanks,
Philip
 
Back
Top