Re: Building my own class library framework

On Dec 5, 7:00 am, Ludwig <lstuyc...@xxxxxxxxx> wrote:

<snip>

What about this: Yesterday I wrote a test application that reads my
visual studio solution file; then it finds out the visual studio
project files and reads them, en eventually I have a list of all code
files in my solution. I check the ones I want and click a build
button; and then an assembly is build with only the selected code
files. This assembly can then be given to the client, containing only
what he needs.

I also save these profiles so that I can load these settings later and
regenerate the assembly again, or modify the selected code files
first.

Still have to think about versioning, but what do you think about this
approach?

I think it's a maintenance nightmare compared with all your clients
having the same assembly (for any particular version) and using
licensing to prevent use of certain features.

If a client reports a bug, you would need to test against that
particular build, and ensure that whatever fix you put out doesn't
break any of the other myriad combinations. Furthermore, every time a
customer needs a new version you need to go through the same custom
build procedure.

Jon
.