Immediate Window is missing in Visual Studio Menu
When you do not see “Immediate” window under Debug menu of Visual Studio you may get frustrated. But there is a quick way to get it when required,
Go to View > Other Windows > Command Window or press Ctrl+W, A
Then type immed. It will bring the Immediate Window.
And inside the Immediate Window if you type cmd it will bring the Command Window back again.
Namoskar!!!
Comments
Anonymous
May 13, 2009
PingBack from http://www.codedstyle.com/immediate-window-is-missing-in-visual-studio-menu-2/Anonymous
May 13, 2009
PingBack from http://www.codedstyle.com/immediate-window-is-missing-in-visual-studio-menu-7/Anonymous
May 31, 2009
Preciso estar linkado com o missing in VSMAnonymous
August 10, 2010
The comment has been removedAnonymous
October 06, 2010
This is mainly the ONLY window i use. Why would MS make it so irritating to find? They seem out of touch with developer needs.Anonymous
January 05, 2011
Or you can simply type Ctrl+G and it will bring up the Immediate Window.Anonymous
May 16, 2011
Thank YouAnonymous
June 20, 2011
I find the same thing - Microsoft always seems to make the most useful things the hardest to find. The most irritating example is the Navigate Forward/back toolbar buttons that are a HUGE timesaver. Yet, they don't ever seem to appear on any of the toolbars - instead you get all kinds of similar looking icons that do some oddball function you'll never use....Anonymous
September 01, 2011
Thank you very much, I was very frustrated trying to get it back and now finding it anywhere.Anonymous
September 29, 2011
Or in Visual Studio 2010 goto Debug > Windows > ImmediateAnonymous
March 05, 2012
thank you - simple and straight forward answer without straying from purposeAnonymous
June 15, 2012
many thanks - I was going mad trying to find it.Anonymous
October 28, 2012
THANK YOU.Anonymous
November 20, 2012
Thank you.Anonymous
October 28, 2013
There isn't the option of a Command Window under Other Windows (or anywhere else I've looked) in VB.NET 2008 Express. Maybe it's only in the Full Version. It's very frustrating not being able to check simple functions as to their being equivalent to VB6 functions. At present I'm finding VB.NET one of the most user-hostile languages I've used.Anonymous
October 28, 2013
Many thanks EW for Ctrl+G. BUT, and it's a big BUT, the immediate window doesn't work the same as it does in VB6. Even a simple command like Print(3 + 4) generates an error. I couldn't do anything in the Immediate Window that didn't generate an error. Can anyone tell me how I can display the result of a simple function call? Why does Microsoft make things so complicated? I've been a software developer for over 30 years (mostly non-Microsoft) but with over 10 years of VB6, so it's not as if I'm new to Microsoft's peculiarities. They just seem to be committed to "Change for the sake of change" and obviously haven't a clue about supporting users. Look at the Win8 user interface, or the Office ribbon.Anonymous
January 10, 2014
Thanks. This is very helpful for me...Anonymous
February 03, 2014
Thanks man, this was giving me an issue.Anonymous
May 28, 2014
The comment has been removedAnonymous
June 30, 2014
For VS 2013, its in DEBUG > Windows > Immediate OR Ctrl + Alt + IAnonymous
October 22, 2014
The mystery is solved. Microsoft does not use any of their own products, this is why they make them hard to use and unreliable. Either that, or their QA process goes something like this: "How's it going?" "Fine." "Ready to release the product?" "Yeah, it looks good." "OK, I'll let [insert current executive's name] know."