I am new and stupid. I closed this window:
How this window is called and how to activate it. Make it pop up.
It is the Locals window.
You will find it under Debug -> Windows.
Alternatively, use the keyboard shortcut Ctrl + D + L.
It is only available during a debugging session and is not available on Express editions.
Go to the Debug menu then windows then locals and it will show up. You must be in the middle of debugging to have it show in the list.
The Locals window comes up with you start debugging (hit F5). If you need it back, go to Debug > Windows > Locals while debugging.
Note, you can also get it back if you click Windows > Reset Window Layout (which I've had to use on occasion when windows get really messed up!) Be warned that this will erase any changes you've made to the layout. But sometimes it is worth it!
Related
when I press Start to run my application in VS 2017 Community my Output window disappears. (I use it for i.e. Debug.WriteLine().) How to prevent this?
P.S.
The output window I`m refering to (not the command line window!):
The output window
Thanks
~Julius
After starting your application (debug mode), click View > Output (Ctrl + Alt + O) to show the output window. Stop your application and restart Visual Studio. Next time you run your application the output window should be visible automatically because Visual Studio remembers your opened windows in debug mode.
Prevent it from autohiding using the 'Auto hide' icon in the right top corner (center of the three) of the Output window. That way it will stay docked.
You can make it a docked tab before running your program
On Menu Bar:
Tools -> Options
A Pop-up window appears:
Debugging -> General -> Automatically close the console(scroll down to last)
Check the box and close
It applied to projects for visual studio.
Press Any Key to Continue...
I feel a bit silly about this, but I seem to have accidentally hidden the variables section for debug mode in Visual Studio Code, and can't figure out how to get it back.
The debugger is starting ok (using node.js for debuggging a js file), and I can see Watch, Call Stack, and Breakpoints - but no Variables window. Have attached a screenshot to show the layout.
screeny of VS Code window
Press Ctrl + P to open the "Go to File..." menu and type in view Variables and press Enter. This will show the variables view again.
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.
Every Time I launch a Debug Session VS 2010 pops the Watch/Debug Windows on the left Screen. I then move it manually to the Right One. After ending the session, going back to code, and relaunching a debug session, that damned Watch window pops on the left again. It turns me crazy ! Why isn't VS memorizing where I have put that window ???
Do you stop debug session with Shift+F5 or by quitting application which is being debugged? VS seems to forget window positions if debugging process was stopped by Shift+F5.
I tried the solution I found on this post. Did not work.
Seems like it's the exact same problem as with the find dialog (see this post)
Ended-up docking the heck out of the Watch/debug window into a more "stable" panel (Class view in my case).
This still looks like an annoying known bug in VS 2010. This sucks.
Visual studio 2010 has at least 3 screen modes.
Normal
Full
Debug
You should export the window settings after entering into the desired screen mode(in your case, debug).
Steps
Start 'debug' your project
Move the desired windows(watch/debug) to the 2nd monitor on right
Goto Tools>Import and Export Settings>Export selected environment settings>General Settings>Window Layouts and export it into a file.
Load the settings by using the import settings in the same window
Visual studio would remember your settings and would move the window to the 2nd monitor on the right, whenever you enter 'debug' mode.
As a tip, it is a great idea to create macros to load window settings and to assign keystrokes to switch between window modes, depending on the kind of development you are on.
code to create a macro to import a vssetting file:
DTE.ExecuteCommand("Tools.ImportandExportSettings", "-import:Path to VSSetting File")
I have become accustomed to using F6 to compile the current document. A third-party install appears to have turned this function off. (F6 no longer does anything.)
Can anyone tell me how to get it back?
I'm using VS2008
Tools > Options > Keybord
This dialog lets you bind keyboard shortcuts to your heart's content. BTW this is how you bind keyboard shortcuts to custom IDE macros as well.
Thanks. The dialog: Tools > Options > Keybord
Allowed me to set the keyboard back to Visual C# 2005. So far, this seems to be what I wanted.
VMware's integrated debugging tool did this to me too. You can change this back to whatever you want, but every time you restart Visual Studio your keyboard shortcuts will be changed again.
The only way I could fix this was to remove the VMware debugging tools.
Its become a habit for me to use Ctrl + Shift + B to build my solutions. I know this doesnt answer your question, but I thought I would point it out.
Another keyboard shortcut is use constantly is Alt + Shift + F10. It opens the drop menu from the little red square under a change (the autocorrect type thing, I'm not sure what its called, also works for autocorrect in all the MS apps)