I think it really depends how much code is shared between the three versions and if the applications have been designed from the ground-up with this separation in mind.

If the applications were not designed from the ground-up with this separation in mind then conditional compilation, and use of the Conditional attribute may be the easiest option until the applications are refactored to ease the division.

Solution one you mention is the most common except there would often be a fourth project (Common) which contains classes shared between the three.

Regards,

William Bartholomew

Thank you William,

I already thought about the Common Project, but the compiled result is useless. What do you think?

I wanted to work with 3 different assemblies, and adding all those file links sounds like: not the 'right' way to do it.

Is it possible to manage this - fairly common - situation more elegantly?

Thanks again,

Alberto

Because in this way for the Standard Edition I have to reference the Common.dll and the Basic.exe and for the Pro edition I need to reference the Common.dll, the Basic.dll and the Standard.dll

Doesn't look like the best way? Does it?