Re: Building my own class library framework

On 5 dec, 10:47, Ludwig <lstuyc...@xxxxxxxxx> wrote:
On 5 dec, 10:10, "Jon Skeet [C# MVP]" <sk...@xxxxxxxxx> wrote:





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

true.. maybe I should clarify that I'm not talking about real
'products' that we ship, but rather independent stuff like windows and
web controls, validation methods, a random number generator, and so
on; things than can be used in the client's products (that we also
develop). The idea is that if we can reuse things that are in the
class library, then we have shorter development time - but we don't
want everything in the library that we don't need now to be available
to the customer.

Anyway, as most of you propose, a licensing scheme would be the best
thing to do I guess.- Tekst uit oorspronkelijk bericht niet weergeven -

- Tekst uit oorspronkelijk bericht weergeven -

I was just a few second late in posting my findings Ludwig. You came
to the same conclusion I had. It could turn out a nightmare
maintaining all different versions for different clients.
If the license option is feasable, I would go that way. If providing a
new license key (file, registry entry) is sufficient to unlock new
features in an assembly, that would be great.

kind regards,
Pascal
.

Loading