I have been using VS 2013 for a month now and recently, ctrl+F5 has not been working. I can build the source file successfully, but when I try to debug, either using ctrl+f5 or f5 alone, All I get is a blank console.
I have repaired the installation but to no avail.
To my understanding, there are three possible diagnoses for your problem that you can attempt to solve.
1. You have an F-Lock key on your keyboard you have accidentally pressed.
Should this be the case, you should search whether your system does indeed have an F-Lock key and ensure that it is disabled accordingly.
2. You somehow have an incorrect keyboard mapping / incorrect settings in VS.
Go in Tools -> Options -> Environment -> Keyboard, select the drop-down for Keyboard Scheme and ensure that your keyboard mapping is correct (the f5 key is mapped to something). You can always also try resetting all of your keyboard settings here.
3. Your f5 key is broken?
Seems kind of ridiculous to say but there's always the possibility your actual key may be simply not working.
Hopefully this helps you get it working!
Two which I'd suggest for this would be, check the project properties launch settings "Start Action" if it's a web project.
Also to right click on the primary project you're trying to debug and "Set as Startup Project"
Related
Lately my F12 key does not seem to be working as expected in Visual Studio 2010 Professional SP1. It should go to the definition of what is selected, but instead it's performing the find all references task - Ctrl+K, R.
Does anyone have any ideas how I can fix this? It is getting quite annoying as I routinely use this shortcut - I am working on a large solution where it sometimes locks visual studio briefly trying to find all references.
I have tried going to Tools -> Options -> Enviroment -> Keyboard -> Reset with no success.
One other thing: it only does it sometimes and I am yet to distinguish a pattern when it does and does not work as expected.
Edit:
One thing I forgot to say is that when it does not work, the second time I press F12 it does take me to the definition, it's just the first press that finds all references.
You can set any keyboard shortcut to any command.
Type edit.gotodefinition to select the command and press F12 to assign the key.
like this
Maybe there is more than one definition for the class or function in your project?
I had this problem after copy/pasting a class definition. After pressing F12 on the class name, it first brought up a search result showing both files in which the class name was found. If you press F12 another time, it will jump to the first one in the search results.
Did you know that you can use Ctrl + - (Minus) to jump back? :-)
I experienced this exact misbehavior today with VC++ 2013: pressing F12 was no longer jumping to a method's definition, but was instead showing a list of references to that method.
Turns out IntelliSense is required in order for the command Edit.GoToDefinition to work, which I had disabled this morning. Setting Tools>Options>Text editor>C/C++>Advanced>IntelliSense> Disable IntelliSense back to False fixed the problem.
Delete your SUO file before opening your project in Visual Studio. Unfortunately you have to do this every time before opening your project. This will also work when Visual Studio stopped regenerating the designer files.
I had the same issue where my F12 key was not working nor were any of my other Function keys. After spending some frustrating time Googling I found that my fancy keyboard had the function key locked! So check that too before try the Tools-> Options
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 Eclipse, whenever I double click a tab, it fills the workspace (by hiding all other views like project tree, console, etc).
Is there any way to do this on Visual Studio?
Note: i'm not looking for full screen, just want a way to declutter the workspace but still have access to menus.
Are you after this?
Set shortcuts for the Window.AutoHideAll function and for the Window.ResetWindowLayout function. In order for the ResetWindowLayout to work, you have to export your settings (make sure you select "All Settings") with all windows expanded and then import them again.
ResetWindowLayout will restore all windows to the way they were the last time you imported your settings.
Not with double click on tab, but you can do the same with Shift+Alt+Enter key combination.
This keyboard shorcut was changed to F11 from 1.9.1 vscode version.
All keyboard Shortcuts: https://code.visualstudio.com/shortcuts/keyboard-shortcuts-windows.pdf
I was looking for that, as well, and I now just got used to using full screen (Shift+Alt+Enter), which hides a little too much, which you seem to think, as well, but does in fact still show the menus.
Looks like drby got it on this one. Just FYI. I pinged the VS team to ask about this and here is the response:
"There is no way to reverse the command automatically. For it to work as a toggle we would need to save which toolwindows were auto hidden and which ones were not when the command was run, which we don’t do (it would cause lots of interesting persistence questions, across profiles and VS sessions)."
The idea of a "Unhide All" command is what I suggested. So if you hide all then you can unhide all as well. There might be some windows you don't want to unhide but the 1 or 2 extra windows is better than not having an unhide IMHO.
I have a solution with about 20 projects (that use Devexpress controls) in and when I do a normal solution build (ctrl-shift-B) it says everything is completed sucessfully when in actualy fact it has done nothing. To get it to build i have to right click on the solution and use the batch build option.
I've tried deleting the solution and regetting from TFS and i've even gone as far as reinstalling VS!
Anyone got any clues as to what is going wrong?
Sorry should have added that also tried to build from the main menus aswell.
I've had similar issues. It's a long shot, but right-click your solution and go to Properties -> Configuration Properties. Check to make sure all of your projects have the "Build" option checked.
Perhaps Ctrl+Shift+B has been assigned to one of the "check-to-see-if-it-is-needed-before-building" type of functions?
Check in the keyboard setting:
Right-click the toolbar
Select Customize in the popup menu
Click the Keyboard button in the lower right corner of the dialog
In the new dialog, in the "Press shortcut keys", a bit to the right and below the center, hit Ctrl+Shift+B
Verify that it is bound to Build.BuildSolution
at least that is what it is bound to for me. I notice there is an action named Build.RebuildSolution as well, you should experiment.