programming using end user libraries.

[Guest]

Hi all

I am just wondering if there is a "standard" for how you present an interface to a client for using a library that you created. In C++ you would provide some header files along with your library......but those don't exist in C#. So do you have to create a seperate file of interfaces that the end user would have as the main interface for the library? Anyone know of any examples projects out there?

 

[Peter Rilling]

Since assemblies are self-describing, there is no need for a separate file.
The assembly itself contains all the information necessary for clients to
consume its functionality. Is there something else that you wanted to do?

Hi all,

I am just wondering if there is a "standard" for how you present an

interface to a client for using a library that you created. In C++ you would
provide some header files along with your library......but those don't exist
in C#. So do you have to create a seperate file of interfaces that the end
user would have as the main interface for the library? Anyone know of any
examples projects out there?

 

[Guest]

Ah OK

so by including a library all of the public classes in that library would automatically become available. Guess I am just breaking the shackles of C++

So providing documentation is much more important with this model as that will be the only easy to access reference the client has

Thanks.