Gary,
What you see in the debugger is a representation of the class. For
example, the TreeNode is an object, not a string, and that single line is
the best representation that they feel they can give you (which, btw, is
totally configurable).
If you want more values from the class, you have no choice but to dig.
VS.NET 2005 should be ^better^ at displaying this, as it cleaned up a
good deal of what is revealed in the watch window. However, it still has
the raw view, which is everything that it offers. What I don't get is your
comment about bearing no resemblance to the programmer's view. Basically,
you can see the properties that are exposed through the class. What else
are you expecting to see?
--
- Nicholas Paldino [.NET/C# MVP]
-
mv*@spam.guard.caspershouse.com
"Gary Brown" <ga********@charter.net> wrote in message
news:OC**************@TK2MSFTNGP02.phx.gbl...
Hi,
Is there a resource that lists where a control's variables are put?
VC puts data such as a ListView's Items in fields that bear no
resemblance to the programmer's view. After documenting
them for V2003 I am in the same boat with V2005. MS has
done an even better job of hiding them in V2005.
Also, my V2005 does not always show a variable's class. For
example, a TreeNode will only show its text value. Digging
down a few levels will usually expose the class name but that
is distracting and annoying. Is this inherent or is there a fix?
Thanks,
Gary