Re: Building my own class library framework
- From: "BobF" <rNfOrSePeAzMe@xxxxxxxxxxx>
- Date: Tue, 4 Dec 2007 08:06:02 -0600
"Ludwig" <lstuyck73@xxxxxxxxx> wrote in message
news:01948acb-352c-4125-913d-8dbe04b540d7@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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?
The license idea that others have suggested sounds like the best
approach -if- you're shipping a library to clients for their use building
their own apps.
OTOH, the way I understood your question is that -you- are doing the app
building and you want to be able to only include certain controls from your
library depending on what your client has paid you to do. If this is the
case, I would be interested in what suggestions others might have.
.
- Follow-Ups:
- Re: Building my own class library framework
- From: Ludwig
- Re: Building my own class library framework
- References:
- Building my own class library framework
- From: Ludwig
- Building my own class library framework
- Prev by Date: Re: Building my own class library framework
- Next by Date: Re: DataTableCollection object question
- Previous by thread: Re: Building my own class library framework
- Next by thread: Re: Building my own class library framework
- Index(es):
Relevant Pages
|
Loading