"Jed" wrote:

> Were using lots and lots of private lists that we need to debug in our
> application. Since we upgraded to .NET Framework 1.1 SP1 we cannot any longer
> debug (in VB.Net) any private collections. All we get in for example Quick
> Watch is a message that says: <cannot view indexed property>. To be able to
> actually se the collections items we need to edit in the watchwindow and add
> the index, for example <myprivatecollection.Item(22).SupplierNo> to actually
> see what it holds. This is a MAJOR drawback from earlier version ?!?! What
> has happened ? This goes for all of us Client developers here, 5 of us....
> this is REALLY annoying ! (it DOES work in C# though).
>
> About 4 months ago we used VS.Net 2002, and there were no problems
> whatsoever to debug...
>
> While we were using vs.Net 2003 NO SP we were at least available to debug
> our inhouse developed collections through the syncroot...
>