In VS2008 I could start the debugger (F5) and make changes then re-start the debugger without having to completely stop debugging and then restart. I cannot find the icon or the keyboard-equivalent shortcut for this action in VS2010.
Default is Ctrl+Shift+F5, however you can remap it in Tools - Options - Environment - Keyboard. Search for Debug.Restart command. The icon looks as following in the Debug toolbar:
.
This toolbar only appears when you are in debug mode. It is actually same in VS2008.
Are you referring to 'Edit And Continue' ?
To enable it:
On the Tools menu, click Options. In the Options dialog box, open the
Debugging node, and select the Edit and Continue category. To enable,
select the Enable Edit and Continue check box. To disable, clear the
check box.
Note that if you're using a 64 bit PC, you will have to explicitly set the platform target to x86 instead of Any CPU as Edit And Continue isn't available on 64 bit machines.
I allways do it with ctrl+shift+f5, I don't know if it's another way to do it
Related
I am currently learning assembly and i am using visual studio to do so. however when i went to evaluate the registers there was no option in the debug drop down. Would i need to install it or activate a setting?
Dont have enough reputation to embed a picture sorry.
The registers window can be opened via Debug > Windows > Registers, when the debugger is active. In the normal editor mode, it does not show up as an option. The set of registers shown in the registers window can be changed via the right-click menu.
Make sure you have enabled address-level debugging in Tools=> Options=> Debugging node.
Don't forget to set a breakpoint, then run the the program in debugging mode.
If you still can't see the Register Option, consider the following: Go to Tools => import and Export Settings => Reset all settings.
Check "Yes, save my current settings," in case you may need to get your old settings back for some reason.
Microsoft Reference
Another Reference
Do all the steps and check the things the people above me said but to seek the register option in the drop down window, set the break point and run the program and then go to the dropdown window. Now it should be there.
I would like to have the default window during a debug session be 'Locals'.
I think there a way to do this by blowing away all other devenv settings, but I'm reluctant to do that as the latest R# seems related somehow.
How can I make the Locals window be the default while debugging?
Berryl, I am not really an expert but I hope this helps:
When I am debugging in VS2010, I choose Debug --> Windows --> Local.
That Local windows stays there if I stop and Debug again.
You can also right click this window and choose "Dock as Tabbed Document", which makes it appear as a tab right next to the pages you are currently debugging.
The "Navigate To" function (CTRL + comma) does not work on my solution. It gets stuck on "Found 0 matching results" while the little progress bar stays there but is empty.
I searched for some kind of IntelliSense cache file next to the .sln, but all I found was a .suo file which I deleted but it did not help.
Why is it not working?
I had the same problem. I went to Tools > Options... > Environment > Keyboard and clicked Reset. Yes, it will reset any customizations you had, but I figured that was the problem for me (I had an add-in take over Ctrl-, and even when I disabled the add-in it wasn't working). Resetting the keyboard shortcut customizations did the trick.
The command is not "Navigate-To" but actually Edit-GotoAll and it has the keyboard shortcuts of Ctrl-T and the more known one of Ctrl-, (comma).
Reference Default keyboard shortcuts in Visual Studio
💡 Solution 💡
Here are the steps to resolve
Verify it is working by trying the opposite keyboard shortcut. If both shortcuts do not work type in "Edit Goto All" in the command search/execute box of Visual Studio.
Does the command work? If it does not work then do a reset via Visual Studio Options:
Then verify or add the keyboard command to the command in the mapping after the reset.
Type in "Edit.Goto" in the Window commands containing
Then selected Edit.Goto.All:
If you do not see the mapping (#3)
Add the keystroke in the box where bubble 4 is above and click Assign.
Set OK as shown on bubble step 5.
This is for Chinese user only. This is because of the Sogou Pinyin (搜狗输入法）occupy this shortcut system wide. And it won't release if you just uninstall it.
Go to here to disable it: Language->Advanced settings->Change language bar hot keys
Uninstall it is not working, you need disable that setting then uninstall it.
The Navigate To Feature does not use an on disk cache so that shouldn't be the issue.
The only thing I can think of that would cause this behavior is a bad Visual Studio install. I hate making this suggestion but have you tried repairing the install?
Tools > Options... > Environment > Keyboard and clicked Reset.That will work.If you installed the latest version/framework or re-sharper of visual studio then it may happens...
I just got the same problem and solve it by following the instruction I found here: http://social.msdn.microsoft.com/Forums/en-US/vssetup/thread/2bbab30e-3188-406b-b492-eabf8c2fbc0b/
For Chinese users, if you are using Sogou Pinyin, you can turn off Ctrl + Comma thru this.
Use spyxx_amd64.exe in this answer should work for most cases. https://stackoverflow.com/a/43645062/1179950
However, this didn't work for me... For my case, which is caused by language keyboard hotkey setting in Windows. By Sougou Pinyin though I have uninstalled it..
You can unset this in Control Panal (Windows 10):
Region&Language -> Advanced keyboard settings -> Language bar options ->Advanced Key settings panel
Unset all hotkeys you wont use!
For traditional Chinese users, you muse use the old version of new Cangjie.
Ctrl+Comma
I have a development tool that's crashing on launch, and I don't get to see any error messages it throws, or get a chance to debug it, because it shows the Windows 7 dialog for crashed programs, where it says "Windows is checking for a solution..."
I want to have my old school big ass assert dialog box back, with a big "DEBUG" button. I have JIT completely enabled in Visual Studio's options and settings, so I'm not sure why I'm not getting the option.
Use Regedit, navigate to the below path:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\DontShowUI]
Create a DWORD and set the value to 1.
This blog post on raymond.cc contains an expanded version of the steps suggested in Krzysztof John's answer.
Quote:
Turn Off The Error Dialog Via The Registry
Although editing the registry manually is not recommended for average users, sometimes there isn’t a choice because something like the Group policy Editor might not be available in your version of Windows or the group policy method itself doesn’t work. This works on Windows Vista and above.
Open the Registry Editor by typing regedit into the Start search box or the Win+R Run dialog.
Navigate to the following registry key:
HKEY_CURRENT_USER\Software\Microsoft\Windows\Windows Error Reporting
Double click the DontShowUI entry on the right and change its value to 1, then close the registry editor.
. . .
The above registry fix will turn off the popup dialog for the current user, if you want the setting to affect all users on the computer then a similar registry key needs to be created in the registry at HKEY_LOCAL_MACHINE. This key isn’t present by default so needs to be created.
Read More: https://www.raymond.cc/blog/disable-program-has-stopped-working-error-dialog-in-windows-server-2008/
control panel -> troubleshooting -> change settings
In my case this solved same problem:
Control Panel\All Control Panel Items\Action Center\Problem Reporting Settings
set to "never check for solutions"
On my old Windows Vista Home Basic install, the option is hidden in a completely different place beneath the control panel:
Control Panel → Classic View → Problem Reports and Solutions → Change Settings → Advanced Settings → “For my programs, problem reporting is: [×] Off”
On one of my two computers I see following behaviour:
Each time I press F10 (Step over) or F11 (Step Into) in the disassembler window, the focus is switched to the source view, resulting in next F10 / F11 done on the source level unless I switch focus back.
Can anyone recommend me what settings to inspect, or what to try to stay in the disassembler view?
Did you try to reset settings on your VS?
from the Visual Studio command prompt window type devenv /ResetSettings
Look in the Tools > Options > Environment > Keyboard section, and check what F10/F11 are currently assigned to (although I can't believe it's something that simple)
Copying the settings from the working computer might solve it. You don't mention what version you're running, but I think they're in the same location in 2005 onwards : My Documents\Visual Studio 2005\Settings\CurrentSettings.vssettings. There's always the Import and Export Settings Wizard too.
Try setting a breakpoint in the assembly view. I'm assuming the existing breakpoints are in the source view.
Could it perhaps be: Tools->Options->Debugging->Enable address-level debugging?
I just tried in VS05, and when I have that unchecked, I can't even bring up the disassembly view, but I would guess that if you somehow got into disassembly view, having that option off would kick you out of disassembly view when you did a step over/into.
Close the source file window ? I had the inverse problem that cause F11 to always debug in assembly, it was fixed by closing the assembly window. May be it works in reverse too ?
Not sure, if this would work but... try if you can?
Open RegEdit
Browse to HKEY_LOCALMACHINE -> SOFTWARE -> Microsoft -> Internet
Explorer -> Main
Add a DWORD under this key called TabProcGrowth
Set TabProcGrowth to 0 (zero)
This is what I used when VS2005 debug mode stopped working (0:
Try removing any .pdb files from the directory you are executing from. Also make sure your Options->Debugging->Symbols settings aren't pointing to any pdbs for the files in question.
Of course I'm assuming you've been through all the other Options->Debugging options, including the native section.