StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>If 2013 works the same as previous versions, then do the following:</p> <ul> <li>Navigate to Tools > Import and Export Settings </li> <li>Choose "Import selected environment settings"</li> <li>On the next screen, choose to save your current setings if you want to. </li> <li>When you get to the point where you can import, just select "General Development Settings"</li> </ul> <p>That should set everything back to what you're probably used to. Most people are set up using general settings and either don't realize it or just forget.</p> <p><strong>EDIT</strong>: If your issue is that the program executes when you press <kbd>F10</kbd> or <kbd>F11</kbd> when you are <em>not</em> debugging, then I think you might be out of luck. It's done that to me personally since VS 2008 (I'll frequently miss the <kbd>F12</kbd> key when I'm in a hurry), and, after some searching, I think it actually happens to everyone:</p> <ul> <li><a href="https://stackoverflow.com/questions/9805201/visual-studio-prevent-f11-from-starting-the-debugger">Visual Studio - Prevent F11 from starting the debugger?</a></li> </ul> <p>My guess is that this is a side-effect of not being able to set contextual hot keys based on whether you are or are not debugging. Since <kbd>F10</kbd> and <kbd>F11</kbd> are tied to debug-execution-related operations, my guess is that Visual Studio realizes that it needs to be debugging to process them, and thus starts the program.</p> <p><strong>ANOTHER EDIT:</strong> Of course, it's also possible that you had the scheme set to something else entirely in VS2012. Check out all of Visual Studio's pre-defined hotkeys by environment here: <a href="http://msdn.microsoft.com/en-us/library/da5kh0wa(v=vs.120).aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/da5kh0wa(v=vs.120).aspx</a></p> <p>If none of those have the mappings that you're used to for <kbd>F8</kbd>, <kbd>F10</kbd>, or <kbd>F11</kbd>, then it's possible that you or an add-on may have had few custom hotkeys defined.</p> <p>Worst-case scenario, you can simply redefine your shortcuts manually by key in the keyboard settings: Tools > Options > Environment > Keyboard</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload