Is it possible to add a class, coded within a separate .cs file, that
is available only within the project?

I hope that is clear. In more detail - I want to write a DLL for
distribution that exposes one public class. I have some utilities
classes that I would like to use in my public class but not expose to
the end user. I was hoping that I just include the source file.

What I'm trying to do is make a "private" class, but that's not allowed
as I'm trying to use it.

I suppose that I could make a separate DLL for the utility classes and
then reference that DLL from the main DLL.

Mike Buchanan

Have a look at the internal access modifier:
http://msdn2.microsoft.com/en-us/library/7c5ka91b.aspx

Greetings,

Wouter de Kort:


<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Is it possible to add a class, coded within a separate .cs file, that
> is available only within the project?
>
> I hope that is clear. In more detail - I want to write a DLL for
> distribution that exposes one public class. I have some utilities
> classes that I would like to use in my public class but not expose to
> the end user. I was hoping that I just include the source file.
>
> What I'm trying to do is make a "private" class, but that's not allowed
> as I'm trying to use it.
>
> I suppose that I could make a separate DLL for the utility classes and
> then reference that DLL from the main DLL.
>
> Mike Buchanan
>

(E-Mail Removed) wrote:
> Is it possible to add a class, coded within a separate .cs file, that
> is available only within the project?
>
> I hope that is clear. In more detail - I want to write a DLL for
> distribution that exposes one public class. I have some utilities
> classes that I would like to use in my public class but not expose to
> the end user. I was hoping that I just include the source file.
>
> What I'm trying to do is make a "private" class, but that's not allowed
> as I'm trying to use it.
>
> I suppose that I could make a separate DLL for the utility classes and
> then reference that DLL from the main DLL.
>
> Mike Buchanan

Mark the classes as internal, rather than public/private/protected and they
will be accessible only within your assembly. So you will be able to use
them throughout your assembly but they will not be accessible to anyone who
is referencing your assembly.
--
Tom Porterfield