Re: Hide private variables.
It may not be possible because it makes sense that the debugger shows field values, but if it is possible then I'm sure that it would involve applying an attribute to the field declaration. If I was trying to achieve this I'd go to the MSDN documentation for the Attribute class, click the link for the list of derived classes and then look down the list to see if anything has a name that suggests that it's used for that purpose. That's what I have always done if I want to modify design time/debugging behaviour.
Re: Hide private variables.
Quote:
Originally Posted by jmcilhinney
It may not be possible because it makes sense that the debugger shows field values, but if it is possible then I'm sure that it would involve applying an attribute to the field declaration. If I was trying to achieve this I'd go to the MSDN documentation for the Attribute class, click the link for the list of derived classes and then look down the list to see if anything has a name that suggests that it's used for that purpose. That's what I have always done if I want to modify design time/debugging behaviour.
Hi jmcilhinney! Thanks for the suggestion but I’ve already done that and didn’t see any thing close to the solution. I even used my vb advanced book and all it talks is about Property and method attributes. No indication what so ever about member variables. Anyway thanks again.
Re: Hide private variables.
Why would you want to do this?
Re: Hide private variables.
It isn’t a big deal but when I have bunch of private variables and public properties it is getting messy to check the values in debug time. I don’t see any class private variables when I use some .Net classes so I though It is possible to do it the same.