Hide 'empty' namespace from extarnal assemblies.

[Michael S]

Hi.

I am working on a class library where I have a namespace called
MyProject.Implementation.
This namespace only have internal and private classes.

However, when I use my .dll assembly in a WinForm application, that
application can still see the namespace via Intellisense. For the consumer
it appears to be an empty namespace.

As access modifiers are not allowed on namespaces, is there another way to
signal, to visual studio (or other tools), that the namespace should be
'invisible' to outside consumers? An attribute perhaps?

Best Regards
- Michael Starberg

 

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

Hi.

I am working on a class library where I have a namespace called
MyProject.Implementation.
This namespace only have internal and private classes.

However, when I use my .dll assembly in a WinForm application, that
application can still see the namespace via Intellisense. For the consumer
it appears to be an empty namespace.

As access modifiers are not allowed on namespaces, is there another way to
signal, to visual studio (or other tools), that the namespace should be
'invisible' to outside consumers? An attribute perhaps?

The only attribute I know of for this is EditorBrowsable:

[System.ComponentModel.EditorBrowsable(System.ComponentModel.EditorBrowsableState.Never)]

not sure if you can apply it to a namespace though, you can try and post
back yor result

 

[Michael S]

Error 1 A namespace declaration cannot have modifiers or attributes
D:\Projects\coredc\trunc\Implementation\DcConnection.cs 9 1 CoreDC

Guess I have to live with the empty namespace. No big deal.

- Michael Starberg

Hi,

Hi.

I am working on a class library where I have a namespace called
MyProject.Implementation.
This namespace only have internal and private classes.

However, when I use my .dll assembly in a WinForm application, that
application can still see the namespace via Intellisense. For the
consumer it appears to be an empty namespace.

As access modifiers are not allowed on namespaces, is there another way
to signal, to visual studio (or other tools), that the namespace should
be 'invisible' to outside consumers? An attribute perhaps?

The only attribute I know of for this is EditorBrowsable:

[System.ComponentModel.EditorBrowsable(System.ComponentModel.EditorBrowsableState.Never)]

not sure if you can apply it to a namespace though, you can try and post
back yor result

 

[Ben Voigt [C++ MVP]]

Error 1 A namespace declaration cannot have modifiers or attributes
D:\Projects\coredc\trunc\Implementation\DcConnection.cs 9 1 CoreDC

Guess I have to live with the empty namespace. No big deal.

How about using an internal static partial class instead of a namespace?

- Michael Starberg

Hi,

Hi.

I am working on a class library where I have a namespace called
MyProject.Implementation.
This namespace only have internal and private classes.

However, when I use my .dll assembly in a WinForm application, that
application can still see the namespace via Intellisense. For the
consumer it appears to be an empty namespace.

As access modifiers are not allowed on namespaces, is there another way
to signal, to visual studio (or other tools), that the namespace should
be 'invisible' to outside consumers? An attribute perhaps?

The only attribute I know of for this is EditorBrowsable:

[System.ComponentModel.EditorBrowsable(System.ComponentModel.EditorBrowsableState.Never)]

not sure if you can apply it to a namespace though, you can try and post
back yor result