Groups | Blog | Home
all groups > visual studio .net debugging > april 2006 >

visual studio .net debugging : How to view a class variable detail in quick watch


Dav Tan
4/27/2006 11:30:30 AM
Hi,
I am debugging a VB.NET application in VS.2003. When I open a quick watch
for a variable (class), I can only see the type of the class, not the list
of members we had in the class (by clicking +). Did anybody have the same
experience? Any idea?

DT

jetan NO[at]SPAM online.microsoft.com (
4/28/2006 2:24:42 AM
Hi Dav,

Thanks for your post!

Can you show me in what context do you get this problem? When you are
viewing the class variable? If you move the curor onto the variable, does
the tooltip information pops up?

Regarding this situation, I suggest you create a simplest VB.net project in
your VS.net2003 IDE, can this problem be reproduced out? If the answer is
yes, you may try another machine with VS.net2003 installed.

Thanks

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Dav Tan
4/28/2006 11:50:27 AM
Thanks for the reply.
[quoted text, click to view]
I set a break point, and when it breaks, I check the class in Quick Watch or
add it the watch list, they are the same thing. Only show the class type, no
class members .. For example, if you get a exception:
////////////////
Try

Catch e as Exception
' do something and try to see the what's inside the 'e', but I can not
End Try
//////////////////////

[quoted text, click to view]
If I move the cursor the class, I can see it showed class type.

If I create a single VB.NET project, and try to debug, everything is fine,
and I can see everything. I experience this in several solutions, and also
in different machines, all of the had more than 5 projects in it. It seems
to me is a VB.NET common problem.

Any idea?

Thanks,
DT

[quoted text, click to view]

Dav Tan
4/28/2006 12:33:27 PM
This link expressed the same problem that I had:
http://groups.google.com/group/microsoft.public.vsnet.debugging/browse_thread/thread/4a625d00fe28dd89/7b17725c964ebffe?lnk=st&q=vb.net+debug+watch+issue&rnum=3&hl=en#7b17725c964ebffe

DT

[quoted text, click to view]

jetan NO[at]SPAM online.microsoft.com (
5/1/2006 3:11:13 AM
Hi Dav,

Thanks for your feedback.

Yes, I see your concern. It seems that this problem may be your project
specific. What is your project type? Asp.net, winform or console?

Because we have never seen this problem, it is hard to give a definite
solution with the information you provided.

Regarding your problematic solution, can you try to remove the projects one
by one out of the solution? Then we can identify which project caused this
problem. Thanks

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
AddThis Social Bookmark Button