Mike,

Typically, the Immediate Window is used in debugging. While debugging, you can use it to change the value of variables if you need to. Or use it to see the value of something (of course you have the Watch and Local windows for that). Or use it to see what would happen if you changed your code to something else while debugging. I used to use it a lot while debugging in VS2003, because that version's IDE didn't have Intellisense in the Watch window (or it didn't work too good, or something ... I don't remember exactly). Not a problem with VS2005 though.

In fact, I never even thought about trying it while just coding. It works, but you're right that it compiles the project first. Interesting. Well, you can comment out stuff that prevents a clean compile while you're messing with stuff in the Immediate Window.

BTW, you don't have to use the "?" to display anything. If you had just typed DatePart(DateInterval.Month, Now) without the ?, it still shows the result.

~~Bonnie




>I've been given the task of maintaining some VB.NET code. After quickly scouring the code, I decided to try to see what some of the VB functions in it was trying to accomplish. So being a long time VFPer and a newbie to VB.NET, I figured I'd open the Immediate Window, enter the function then see the result. I hoped that it would behave like the VFP debug window where I'd see the immediate results :)
>
>Was I wrong. After typing "? DatePart(DateInterval.Month, Now)" into the Immediate window without the quotes, .NET decided to build the project. Of course, with all the errors and warnings, I don't get to see the result of what I tried to type. Just out of curiousity, I then typed "? 100/10"...same thing! Nothing.
>
>Was I expecting too much from this .NET IDE "Immediate window" thing? If not, how do I make it work such that I can get a result returned/displayed to me when I type in simple commands/functions?
>
>TIA