Home/ Questions/Q 3313412
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T22:06:45+00:00

I have the idea that it might be useful to enforce type visibility between

  • 0

I have the idea that it might be useful to enforce type visibility between namespaces rather than assemblies (internal) in C#.

It would seem that such a concept would assist developers working with a codebase, ensuring the correct types are used in places where another internal type supplying similar functionality is available, but would result in “architectural” disadvantages (unwanted dependencies etc).

Do others think this would be useful and is it currently possible? If not why not?

Also, would the concept of preclusions – the ability to specify negative constraints on references between namespaces and / or assemblies be a useful addition to C#?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You could make them public, tag them with a custom attribute, and then add a FxCop rule to check for accesses from the outside of the namespace.

    This doesn’t securely enforce the restriction and fails when the member is accessed with reflection, but if it’s only about policy/codingstyle this should be enough.

    I think there is also an existing attribute to hide members from Intellisense which you might use in conjunction with your custom attribute.

    • 0