Different behavior in debugger between VB.NET and VC#

[LF]

Hi,

Why is it when you build an assembly in C# and it has a private fields in a
class, they are not visible in the Watch/QuickWatch window when referenced
and debugged
from VB.NET project.

But if you build VB.NET assembly and reference it in VB.NET project, you do
see private members in Watch/QuickWatch window during debugging.

What's the reason for this? Any way to make it work with C# assemblies in
VB.NET debugging session?

Thank you

 

[Gary Chang[MSFT]]

Hi,

Currently I am looking for somebody who could help you on it. We will reply
here with more information as soon as possible.
If you have any more concerns on it, please feel free to post here.


Thanks for your understanding!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Peter Huang [MSFT]]

Hi

I can reproduce the problem on my side, and I have reported the problem to
our related team.

So far as workaround we can monitor the private field forcely.

e.g. cs is a C# class instance with private field str.

Although we can not monitor the cs's str when we add cs into watch window,
but if we forcely input cs.str in the watch window and we can watch the
value of cs.str.

Hope this helps.

Best regards,

Perter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.