调试器无法继续运行进程。无法启动调试器

我有一个 Lightswitch 2012的申请。已经好几周了。我做了一些改变,F5停止工作。当我点击开始(工具栏) ,它给出这个错误消息,什么也不做。

“调试器无法继续运行进程。无法开始调试”

注意: 它可以编译文件,只是不能运行。

如果我回滚到早期版本,那么它工作得很好——也就是说,它是特定于解决方案的。

下面是我解决这个问题的当前版本的视频: Http://screencast.com/t/td4rzlaso

这是今天早些时候的解决方案的前一个版本(不,我不知道我改变了什么)。正如你所看到的,至少它对 F5或 Start 做了一些事情: Http://screencast.com/t/wx5frdpz

重新启动没有帮助... ;)

41538 次浏览

Maybe you should select start up project which can be started.

Solution Explorer -> On your startable project right mouse click -> Set as Start up Project.

I had this situation when i unloaded my main lightswitch project and other project which is dll has been selected automatically and when i reloaded my main project "The Debugger cannot continue running the process. Unable to start debugging" exception was shown, because debuger was trying to load DLL.

Sometimes you need to start up a project which is compiled as a dll, for instance when testing WCF services. To do so: Projects -> 'Set Startup Projects...' -> Select 'Multiple Startup Projects' and set action to 'Start' for each one.

I encountered this problem after removing some projects from the solution. I wasn't able to pinpoint the exact cause, but closing the solution, deleting the solution file, then opening the project and re-adding supporting projects solved the issue for me. Kind of a sledge hammer, but only takes a minute to do if you don't have a lot of projects.

Also, there are some people that uses a "One Click" Certification in your settings that you'll want to make sure its set up right, re-install or unchecked in-which this case was my problem. I finally got it working myself, but check that too just in case. Again this would be for most Visual Studio Versions only. Im 2013 Ult.

It's a pity you didn't recorded the whole screen, so I can't confirm, but I had the same error a few times...

When this happens, my "output panel" isn't visible and even I try to go on Menu -> View -> Output the panel don't appear.

I need to restart my Visual Studio 2013. Then my output panel is visible again and everything works fine.

I discovered the cause was an extension which I installed on my Visual Studio.