Compiling a Class Library project into multiple assemblies

[Guest]

Hi there,

I'm working on developing a large Class Library project that is slowly
becoming a shared "framework" library amongst multiple applications. As this
shared library grows, I need to start thinking about ways to split this
library up.

In observing the .net framework, I've noticed that each major branch of the
framework (eg. System.Net or System.Data) and even some of the minor branches
are split up into individual dlls. When an applications needs a piece of the
framework from System.Data, they simply import that namespace (eg. using
System.Data) and that automatically links in the managed dll for that
namespace.

Is there a simple way for me to do the same thing for my shared library? Is
there a flag somewhere, or perhaps a particular configuration file that I
need to modify in order instruct the compiler to automatically split up my
library into separate dlls as per the namespace hierarchy?

I've tried many web searches on this subject, but all attempts thus far have
produced little fruit. Any help would be greatly appreciated!!

Thanks in advance!

T

 

[Guest]

Add multiple projects to your solution. Each project will have a different
default namespace i.e. MyCompany.Framework.Data, MyCompany.Framework.Text

Each project will compile into its own assembly. You can set up the default
namespace and assembly name in the projects page of the project.

Hope that helps.

 

[Guest]

oops - last sentance of my prior post should have read "properties page of
the project"

 

[Guest]

So there is no way to have the compiler/vs2005 automatically split one
project into multiple assemblies (based on the hierarchy of the namespace)?

Thanks Art for your prompt reply!