VB 6 had the ability to use the immediate window to run a quick function while in design-time. This was helpful for quickly testing the result of a function that you weren't familiar with. As it stands now, we must go into Break Mode in order to test a function in the immediate window.

Is it possible to get that functionality back into the immediate window? Or, if it already exists, how can I make use of it?

Thanks,

I'm not sure if it exists yet, but this one is on the VB.NET team's plate. You'd have to ask one of them for the official word on that though, but I believe it's something they're considering for Whidbey!

Indeed, this is on the VB team's plate. However I think it only works for client projects and not for web projects as it depends on the client compilation model.

Wow, this thread still comes up in search and almost 6 YEARS LATER - still no Immediate debugging without runtime breakpoint-hitting!

I can understand that the Web Project config is nec (the Website model doesn't have a DLL for the client compilation) but after setting all that up, there's still no way of testing code without fiddling around causing breakpoints (annoying with necessary logins etc). Its sometimes cleaner to copy all the methods (and dependancies, Main etc) into a separate executable project, but this seems a ridiculous overhead - haven't web projects moved forward? I appreciate that some webserver-dependant methods would error in this situation but surely the other non-dependant ones could be called?

Will stick with Web Projects because of XML documentation and also Class Diagrams can show the .cs / .vb CodeBehind methods (which the Website model won't do - they only seem to allow selection of the standalone class files for some reason). But surely, if a DLL is compiled in a Web Project, why can't methods (ones not dependant on the webserver itself) be called without running breakpoints? Maybe there's a way through Reflection (another benefit of DLL compilation)?