L
Ludwig
Hi all,
we are building our own class library framework, with stuff in it that
can be used in various projects at various clients.
Initially we had 4 assemblies with everything in it. Of course, when
project A only needs one class, it gets everything in the assembly
also; and we don't want that.
Now we create an assembly for each control or main functionality, so
the project has to add a reference to the assembly it really needs.
But now, we introduce danger for circular references and dependency
issues; it's harder to maintain.
Is there a clean solution to make sure that projects only get the
classes they really need, but without the difficulties of having a lot
of assemblies? Maybe select what components are needed at build time
and then build an assembly with only the needed stuff?
What are your ideas?
we are building our own class library framework, with stuff in it that
can be used in various projects at various clients.
Initially we had 4 assemblies with everything in it. Of course, when
project A only needs one class, it gets everything in the assembly
also; and we don't want that.
Now we create an assembly for each control or main functionality, so
the project has to add a reference to the assembly it really needs.
But now, we introduce danger for circular references and dependency
issues; it's harder to maintain.
Is there a clean solution to make sure that projects only get the
classes they really need, but without the difficulties of having a lot
of assemblies? Maybe select what components are needed at build time
and then build an assembly with only the needed stuff?
What are your ideas?