using Visual Studio 2005

[Guest]

Why do I keep losing Intellisense in the command or immediate window when
debugging? I didn't use to have this happen and sometimes it's available
and sometimes it's not. It's pretty hard to test certain variables when you
don't remember what all the gazillion methods and properties are for a
datareader for instance. I always have to cancel the debug, go back up to
teh code, figure out what the syntax is, then run debug again. Does anyone
know why the intellisense -- sometimes only -- doesn't work in debug mode?

 

[Mark Rae [MVP]]

Why do I keep losing Intellisense in the command or immediate window when
debugging? I didn't use to have this happen and sometimes it's available
and sometimes it's not. It's pretty hard to test certain variables when
you don't remember what all the gazillion methods and properties are for a
datareader for instance. I always have to cancel the debug, go back up to
teh code, figure out what the syntax is, then run debug again. Does
anyone know why the intellisense -- sometimes only -- doesn't work in
debug mode?

It depends what you're debugging - if it's page level stuff, IntelliSense
tends to die when the page times out...

 

[Guest]

That happens to me too, and not just when debugging, but only in
Default.aspx:-(
Also Build ***Always*** succeeds, errors only being picked up by the
compiler when I run the app.

Guy