CODEWITHSUNDEEP
visual-studio-debuggingvisual-studio-2012
Glen Little
Glen Little

Reputation: 7128

Can't start debugger in VS2012 RC

Configuration:

When I press F5, the solution builds... and nothing else happens.

If instead, I use the Debug / Attach to Process... menu, after a few seconds, I get:

Any suggestions or clues?

The main points that I wonder about:

(Cross posted on social.msdn)

Upvotes: 20

Views: 41963

Answers (16)

user222427
user222427

Reputation:

I just closed and reopened VS. This seemed to fix my problem

Upvotes: 1

Adversus
Adversus

Reputation: 2226

Had this problem for a C++ application. Looking at the devenv.exe events in ProcMon pointed me to it trying to load a Visual Assist configuration file, which I had in my disk cleanup zeal accidentally deleted. Removing and then installing the extension again fixed it for me.

Upvotes: 0

Matthias
Matthias

Reputation: 501

I personally encountered some comparable problem: Visual Studio 2010 did not begin debugging but froze.

When I clicked VS it displayed a "Wait some more" or "Switch to" message box which didn't help me.

Using a task manager I could kill the *.vshost.exe process which brought VS back to life but aborted the debugging. Launching the program without debugging started the application instantly.

Solution:

Disable the indexing service for your code directories! Either deactivate the index service or uncheck the folders in the Indexing Service control panel.

Upvotes: 0

IbrarMumtaz
IbrarMumtaz

Reputation: 4393

Just my two cents,

I have experienced this issue twice now and it turns out after all of the suggestions I tried, it was BitDefender on my local machine that was doing this. So my fix for this problem is to try adding in exceptions to the local security software into the firewall and AV parts of it. Tell it to ignore the msvsmon.exe and devenv.exe altogether and see what difference that makes.

Otherwise try ripping it off altogether and see if the it lets you debug your solution.

You can see here for more info: http://forum.bitdefender.com/index.php?showtopic=37028

I installed the latest BitDefender version and all was fine for me.

Upvotes: 0

George Kosmidis
George Kosmidis

Reputation: 359

Just copy all dte*.olb files, from C:\Program Files (X86)\Common Files\Microsoft Shared\MSEnv to C:\Program Files X86\Microsoft Visual Studio 9.0\Common7\IDE.

From https://mycodepad.wordpress.com/2013/12/07/visual-studio-2012-4-run-as-administrator-the-application-cannot-start-error/

Upvotes: 0

Fijjit
Fijjit

Reputation: 1467

For what it's worth, I found that I received this error message when I had an entry missing in my hosts file. I am using local domain aliases and the one I was trying to debug with wasn't in hosts. Adding the missing entry solved the problem for me.

Upvotes: 0

Ghenadie Tanasiev
Ghenadie Tanasiev

Reputation: 1

I have fixed the same issue by checking off the "Enable the Visual Studio hosting process" option from the start-up project Properties->Debug - Enable Debuggers options

Upvotes: -2

armin
armin

Reputation: 2025

If you are opening a VS 2010 project with the new VS 2012 version it's probably your bin and obj folders that are causing the problem,deleting them solved the problem for me.Or you could clean your solution but I preferred manual deletion.

Upvotes: 1

LordWilmore
LordWilmore

Reputation: 2912

I had the same issue - starting debugger just told me what a good job it had made of the build and the decided that that was enough.

I feared the worst, but luckily for me a reboot fixed the problem.

I know that this is therefore a pretty useless post in as far as offering help to anyone suffering with this issue, but I thought it was worth noting the point as it shows a) another person with the same problem so please fix it MS, and b) that sometimes a reboot fixes it so maybe that tells the maintainers something.

Upvotes: 1

DarkN3ss
DarkN3ss

Reputation: 75

All you have to do to fix this is go "Project > Set as StartUp Project" then hit F5 or the debug button and it will work!!!

Upvotes: -3

Joe Loutzenhiser
Joe Loutzenhiser

Reputation: 41

I eventually resolved this problem by deleting the msvsmon*.* entries in the \Windows\Prefetch folder. After doing so I could debug normally.

Upvotes: 4

JG in SD
JG in SD

Reputation: 5607

Seen a similar issue when running both Visual Studio 2010 and Visual Studio 2012 at the same time. Closing Visual Studio 2010 allow the debugger to start working in Visual Studio 2012.

Upvotes: 2

Adam
Adam

Reputation: 51

I had the same problem in VS 2012 (not the RC, but the final release) using a VS 2010 project. It would build fine, but the debugger would not start. So, I modified the solution file:

Changed "Format Verion 11.00" to "Format Verion 12.00" And changed "# Visual Studio 2010" to "# Visual Studio 2012"

It's a workaround for now until my company upgrades its projects to VS 2012.

Upvotes: 5

Glen Little
Glen Little

Reputation: 7128

On another computer, with the RTM of Visual Studio 2012, I opened an older project and found that I could not press F5 to start the application. All that seemed to happen was a message in the status bar on the bottom edge of the window: "This item does not support previewing".

This solution had two projects, and the correct one was bold in the Solution Explorer, presumably indicating that it was the startup project.

However, after selecting the project and choosing "Set as Startup Project" in the context menu, I was then able to use F5 to run and debug it.

It turns out that the "This item does not support previewing" was nothing to do with the problem, but is a message that shows on the status bar whenever the item just selected in the Solution Explorer does does not support previewing.

Upvotes: 0

Matt B
Matt B

Reputation: 8643

I've got a similar setup and I'd followed all the suggestions here and on Microsoft Connect - none of which worked for me. The only thing that did work was renaming MSVSMON.EXE in the x64 folder to MSVSMON.EXE.OLD and copying in the file from the x86 folder in it's place. I'm not sure if there are any other implications in doing this but it seems to have solved the problem in my case.

Upvotes: 3

Steven Bone
Steven Bone

Reputation: 598

Ultimately, a Repair of the VS2012 resolved this issue for me. I followed the advice found at your social.msdn cross-post without any resolution (Devenv.exe /SafeMode /ResetSettings /ResetSkipPkgs and /Setup). Like you, my solution (VS 2010 SP1) also has a web application (targeting .NET 3.5), and the startup project is set to a winforms app. The ASP.NET development server did not start, nor did the app I was trying to debug.

Note that this issue was also posted to Connect at this link (by you?). If anyone else sees this issue, the Connect folks are requesting running the Microsoft Visual Studio 2012 Feedback Tool to collect data. As I started the Repair process prior to finding the Connect issue, I did not and was not able to provide feedback to MS with logging.

Upvotes: 2

Related Questions