Urs,
I'm sorry, you may have missed my point.
My understanding is all the windows of the VS.NET debugger (immediate,
command, watch, autos, locals) use a VS.NET specific expression evaluator (I
understand that it is shared across all languages). If you attempt to enter
valid C# or valid VB.NET those expressions may not work as you expect.
Considering that you could be debugging both a C# & VB.NET project at the
same time, which language should it choose?
This is similar to the expressions expected by DataTable.Compute &
DataColumn.Expression, the DataSet has its own expression syntax that does
not match VB.NET (nor C#) although it is close to VB.NET...
Rather then entering valid VB.NET in the immediate, command, watch, autos,
or locals windows (which you demonstrated has problems) enter source in a
source file and compile it. This way you are guaranteed that you are using
the VB.NET compiler on those expressions, rather then 'something else'...
I'm not finding a KB article on this, I will post something to Microsoft to
see if there is a KB article or other info that identifies this problem.
Hope this helps
Jay