Hi,

The property IsDefaultVisibility on AccessSpecifiedElement doesn't behave the same way it used to in 2.1.3. Now it always seems to report true, before it reported false when you had explicitly set the visibility on a member.

 Why?  

Thanks!

 / Joel

Joel F:

The property IsDefaultVisibility on AccessSpecifiedElement doesn't behave the same way it used to in 2.1.3. Now it always seems to report true, before it reported false when you had explicitly set the visibility on a member.

Hi Joel,

Thanks for the report. We're taking a look at this now.
 

Hi Alex,

Thanks for informing me that it really is a bug and that it will be solved in the next release, but when is that?

I´m depending on a working DXCore for my Code Style Enforcer plug-in, and right now this property makes Code Style Enforcer work really bad. Alot of users have complained about this after upgrading from DXCore 2.1.3 to 2.2.2. It seems really strange how something as trivial to test as this can go through your unit tests, but I guess we are all humans after all .

I can of course make an ugly workaround for the moment, but I rather not, since the whole point with using DXCore is to have a reliable and stable framework at the bottom layer. So please let me know when I can expect a fix for this, so that I in my turn can inform the users of Code Style Enforcer about this.

Joel F:

Thanks for informing me that it really is a bug and that it will be solved in the next release, but when is that?

As I'm sure that you know, it's difficult to estimate release dates and, as a company policy, we don't do it. We do plan on getting a new release out soon to fix several known issues, but the term "soon" is a bit relative I'm afraid.

Joel F:

I can of course make an ugly workaround for the moment, but I rather not, since the whole point with using DXCore is to have a reliable and stable framework at the bottom layer. So please let me know when I can expect a fix for this, so that I in my turn can inform the users of Code Style Enforcer about this.

While not ideal, here's a method that you can use to check this value in your plug-in:

bool IsDefaultVisibility(AccessSpecifiedElement element)
{

  if (element == null)

    return false;

  return element.VisibilityRange.IsEmpty;
}

Using that should correct the problem for you until the next release. We sincere apologize for this inconvenience.