Why can't I look at Items in a collection in the debugger?

[Rob R. Ainscough]

I'm getting very frustrated with VB.NET debugging issues.

Example;

I'd like to see what values are in the Session collection and all I get from
the debugger is "<cannot view indexed property>" -- Using
Session.Keys.Item.

Yet in C# debugger it will show me the Session.Keys.Item??

Can someone explain this to me as I'm completely baffled -- maybe my VS 2003
was just not installed correctly? Or is this Microsoft's way of forcing
everyone to the messy syntax flow that is called C?

Thanks, Rob.

 

[AMDRIT]

I found it annoying myself. However, I did find that I could drill into the
specific value

myds.tables(0)
will not give me each row

myds.tables(0).rows
will give me a row
myds.tables(0).rows(0)
will give me a row

I think it has to do with the way VB uses reflection to provide us the
information. In any event, I haven't found a better way.

 

[Rob R. Ainscough]

But it is available in C# -- which is really confusing me. I really hope
this is addressed in VS 2005 unless MS are thinking they just want to
support one language and C# will be that one language. I don't mind C#, but
it just doesn't read as well as VB and for encouraging new developers along
they often prefer the VB syntax over C#. Both languages do the same, but I
don't understand why important debugging features were left out of VB.