Re: RE: Silverlight binding to IsDirty doesn't change when other properties are changed

JonnyBee posted on Wednesday, December 30, 2009

Hi Rocky,

You may consider changing from [Browsable(false)] to   [EditorBrowsable(EditorBrowsableState.Never)] on the Is... flags.

The tricky part is that EditorBrowsable is only honored for assemblies/references that are not part of the solution itself. IE:  It is not honored for projects that are part of the solution.

But - with these limitations - applying EditorBrowsable to Is.. properties in Csla will hide Is... flags from the designers like DataSource Explorer but still allow databinding to be manually configured in Windows Forms. 

RockfordLhotka replied on Wednesday, December 30, 2009

I am not sure I like that though either Jonny. The reason being that this would make the properties invisible to a lot of people's intellisense. I can just imagine all the confusion as some people see the properties and other people don't (depending on their VS settings).

This is already an issue with things like the EditLevel property, which is set to either Never or Advanced. That is the correct setting for EditLevel, because it shouldn't normally be used (it is there for diagnostic purposes), but people get confused when they can't see it in intellisense and they assume it isn't actually there at all...

I can live with that for EditLevel, but not for something that should be commonly used like IsDirty.