Defining .NET Components with Namespaces

Posted on Simple Talk See other posts from Simple Talk
Published on 14 March 2011 Indexed on 2011/03/15 0:16 UTC
Read the original article Hit count: 272

Filed under:
A .NET software component is a compiled set of classes that provide a programmable interface that is used by consumer applications for a service. As a component is no more than a logical grouping of classes, what then is the best way to define the boundaries of a component within the .NET framework? How should the classes inter-operate? Patrick Smacchia, the lead developer of NDepend, discusses the issues and comes up with a solution.

© Simple Talk or respective owner

Related posts about .NET Framework