Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / IDE / October 2007

Tip: Looking for answers? Try searching our database.

Command vs Immediate Windows

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
WJB - 29 Oct 2007 20:14 GMT
Hi,

Here's a very novice question. I accidentally closed my Immediate Window and
cannot open it again. According to the VS Help, it should be available as a
selection from the Debug|Windows menu. But it isn't. I can still use the
Command Window to display variables, etc. But how can I re-open the Immediate
Window as it is more convenient being there as a tab along with Watch, Call
Stack and Output? Is there a key combination that I can use to open it?

Thanks
Scott M. - 30 Oct 2007 00:39 GMT
The Watch, Call Stack and Output windows are not part of the Immediate
window.  They just happened to be docked to it in a tab fashon when you
closed the Immediate window.  You can get all these windows back by going to
the Debug...Windows or Debug...Windows...Other Windows menu choices.

> Hi,
>
[quoted text clipped - 10 lines]
>
> Thanks
WJB - 30 Oct 2007 01:04 GMT
Thanks, Scott. So the Command Window is really the one I'm looking for.

> The Watch, Call Stack and Output windows are not part of the Immediate
> window.  They just happened to be docked to it in a tab fashon when you
[quoted text clipped - 15 lines]
> >
> > Thanks
Scott M. - 30 Oct 2007 15:42 GMT
You won't see a window named "Immediate" in the menu choices, but you will
see the "Command" window listed.  When the window appears, it will say
"Command - Immediate" in its title bar.

> Thanks, Scott. So the Command Window is really the one I'm looking for.
>
[quoted text clipped - 21 lines]
>> >
>> > Thanks
Scott M. - 30 Oct 2007 15:48 GMT
Actually, it looks like I'm wrong on this.  In VS .NET 2003, the Immediate
Window was renamed/became part of the Command Window.  In 2005, it looks
like it's back to being available as the "Immediate Window".

Also, you mentioned not seeing the appropriate choices when you look at the
Debug > Windows > Other Windows menu.  That's because you have to be in
break mode to see some of these choices.  When you set a breakpoint and run
your code to it and the debugger breaks on it, then go to that menu and you
can turn on your window choices.

> You won't see a window named "Immediate" in the menu choices, but you will
> see the "Command" window listed.  When the window appears, it will say
[quoted text clipped - 26 lines]
>>> >
>>> > Thanks
Joe Fawcett - 30 Oct 2007 17:05 GMT
And you can type immed to get the immediate from the command window. And
>cmd to go back.

Signature

Joe Fawcett (MVP - XML)

http://joe.fawcett.name

> Actually, it looks like I'm wrong on this.  In VS .NET 2003, the Immediate
> Window was renamed/became part of the Command Window.  In 2005, it looks
[quoted text clipped - 37 lines]
>>>> >
>>>> > Thanks
WJB - 30 Oct 2007 20:04 GMT
Thanks, Joe. Very useful to know. Still, the Debug|Windows menu has no
Immediate entry, so it can't be invoked that way. Interestingly, once it is
invoked after typing Debug.Print (or ?) commands or the immed command, the
Immediate appears again, but with no tab until I switch over to Watch, Output
or Call Stack, and only then does the Immediate tab appear alongside the
other 3. The Debug|Windows menu still doesn't show it, however. I don't know
if this is a VS bug or by design! Anyway, as long as it can be invoked
somehow, I suppose it's ok.

Thank you again, and than you too, Scott, for your help.

I do have 3 other posts that I haven't been able to get answers on. I wonder
if you can help me out there too. They are:

* Upgrading from IIS 5.1 to IIS 6.0 (in iis.security)
* Publishing Simple Web Site (in aspnet.security)
* Problem with FormView Delete and Update when using CompareAllValues (in
ASP.NET Forums » General ASP.NET » Data Presentation Controls)

Thank you again,

WJB

> And you can type immed to get the immediate from the command window. And
>  >cmd to go back.
[quoted text clipped - 40 lines]
> >>>> >
> >>>> > Thanks
Scott M. - 30 Oct 2007 20:20 GMT
You can always go Tools > Import / Export Settings and then choose to reset
all settings to try and restore everything back to its inital state.

> Thanks, Joe. Very useful to know. Still, the Debug|Windows menu has no
> Immediate entry, so it can't be invoked that way. Interestingly, once it
[quoted text clipped - 78 lines]
>> >>>> >
>> >>>> > Thanks
WJB - 30 Oct 2007 23:13 GMT
Thank you, Scott. I'll probably do that some time.

> You can always go Tools > Import / Export Settings and then choose to reset
> all settings to try and restore everything back to its inital state.
[quoted text clipped - 81 lines]
> >> >>>> >
> >> >>>> > Thanks
Scott M. - 30 Oct 2007 15:43 GMT
Just to be clear, you can get the Command window back in the same manner as
all the other windows.

> Thanks, Scott. So the Command Window is really the one I'm looking for.
>
[quoted text clipped - 21 lines]
>> >
>> > Thanks

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.