page 1 of 1
Comments: 4 | Views: 1558
#Jan 27th @ 4:07 AM
JChung2006
JChung2006

Visual Basic variables of the System.Guid type show up as Guid.Empty instead of their actual values when displayed in the Visual Studio debugger windows (Locals, Watch, etc).

This bug affects both Visual Studio 2005 and 2008.  System.Guid variables show up fine in C#.

#Jan 27th @ 4:31 AM
stevo_
stevo_
Casablanca != Manchester
Interesting, it replicates here.. I wonder if this behavior has been previously documented.. seems odd it wouldn't of been noticed before (personally I rarely do vb, so, yea)
#Jan 27th @ 7:11 AM
jonm
jonm
Blah..
I filed a bug about this in the VS2005 beta.  I was told that it was not going to be fixed.  I was also told that I could write my own custom visualizer.  The MS tech even sent me sample code.  Sadly I could never get it to work.  I have come across articles on creating visualizer but have not taken the time to work on it.  Link Below -

http://msdn2.microsoft.com/en-us/library/ms379596(VS.80).aspx
#Jan 27th @ 10:11 PM
numedia
numedia
I bet if you call .ToString, you will see the GUID in all its glory.
#Jan 28th @ 1:11 AM
littleguru
littleguru
allein, allein,... allein, allein!
numedia wrote:
I bet if you call .ToString, you will see the GUID in all its glory.


Probably... interesting that the VB.NET watch window isn't calling that exact same method when no visualizer is specified... Perplexed
page 1 of 1
Comments: 4 | Views: 1558