I am working on a C# project in Visual Studio 2010 express, I have a breakpoint that only shows up when I am in the debug modus, I can remove it there, but it will show up again as soon as I start the debug modus again. Allways on a specific codeline, I tried to leave that line empty, then it jumped to the next one. It didnt showed up as I comented the whole code after that line out.
I dont have a breakpoint window in the debug menu ( maybe because it is the express version) so I can't acces to the "remove all breakpoints" function. Do I have to do some change in one of the debug files? Wich one?
thanks
Related
The debug type field is greyed out as are the build buttons. I opened a folder in visual studio 2019 with my project and source code files. I have not installed any extensions yet either. I read somewhere to select a startup item but none of the items in the solution explorer are valid except for Gradebook.dll in the debug folder although that doesn't seem to do anything.
Did you try to click the run button or press F5.
If so it should prompt you to select CPU. Then, run it again and it should work.
If that doesn't work try going into "Program.cs" in the Solution Explorer and make sure the Application.Run line is there.
I have an application(not mine) that just seems to hang. I would like to see what it's trying to process, or if it's processing anything. Is that a button in visual studio that I can click that will break at the point it's trying to process?
If you click on the left side of the editor (the place where you actually edit the text), then you will set a breakpoint on that line. When debugging, if your program reaches that line of code, then Visual Studio will stop running your program and let you debug it.
So just set a breakpoint immediately before where you think the problem is.
It would be very helpful if we can find a keyword, and set breakpoint at all the search result lines.
Is it possible in Visual Studio, preferrably without a third party add-on?
Under Edit menu - go to Find and Replace
Then under Debug menu - New breakpoint
Then OK
I just switched to Visual Studio 2010, and now whenever I select something, Ctrl+C to copy, click somewhere else, and Ctrl+V to paste, I get an error message "Cannot navigate to definition." After that, it I try it again, it works. What fantastic new 'feature' should I be turning off to stop this?
Bah, it's a bug in Microsoft Productivity Power Tools for Visual Studio 2010. the "Ctrl+Click Go To Definition" feature. Apparently, when I click a new location and then press "Ctrl+V" - if I do it quickly enough, it interprets it as a Ctrl+Click and immediately tries to trigger a navigation, even if I clicked on an empty space. The error comes because it doesn't know what I'm trying to navigate to (answer: I'm not).
I have/had similar issues in VS 2012 (Premium).
I've tried the following:
removed all bin and obj folders from project's folder: works most of
the time.
repaired VS 2012 (add/remove bugrams (programs) > repair). Didn't
help much.
Close and opened VS 2012: didn’t help much either.
I've noticed than I couldn't open only files that weren't check-in in
TFS. I check-in them and then VS started working normally.
Dunno if this issue will appear again tough.
Hopefully this would help someone.
BR
you can remove the GoToDefProPack.dll file from the following location:
C:\Users(myUserName)\AppData\Local\Microsoft\VisualStudio\10.0\Extensions\Microsoft\Productivity Power Tools\10.0.20318.14
to disable this feature completely.
While debugging, whenever we step into a method, the file which defines that method will be opened and remains open after debug - this messed up my files in Visual Studio. I want to be able to close those opened-by-debugger files after the debug finished.
Let's say I'm opening 5 files already and start debugging. After the debug, I have 10+ files opened which means there are 5+ "new & strange" files opened by the debugger. I don't want them, and just want to close them quickly
How can I do this?
There used to be a option "Recycle Windows" in former versions of Visual studio, which only added one additional window for all debug windows. But apparently this has been removed.
I have an idea after a while:
You can pin the tab (tab == file) using addon Visual Studio 2010 Productivity Power Tools. Then after the debug just right click tabs area and call "Remove all but pinned".