Multiple Edition management with VS 2005
Hi All,
Here is thebig question:
Suppose to need to compile the Basic, Standard and Pro editions of you app. What will you do inside VS2005? (each edition contains adifferent set of file/classes but, obviously, the most are shared between each app edition)
1) I create 3 project (Basic, Standard and Pro) andlink the shared files/classes from the first.
2) I use conditional compiling, placing the classes inside an #if PROEDITION #endif statement.
3) I build 3 different asseblies and merge them using ILMerge.
4) Other.
Thanks so much for your thoughts, I want to start with the right foot!
Alberto
[739 byte] By [
devdept] at [2007-12-25]
Alberto,
I think it's going to depend on how many differences there are between the different projects. I'd personally probably start with 2. It gives you a single place to control all of the project options, and an easy way to create a configuration that builds each one of your apps. I might choose to go with 1 if the number of changes was very large and those changes were isolated to complete files. I don't think 3 is the right choice.
Hope that helps,
Anson
Hi Anson,
Thanks a lot for your thoughts.
My Basic project has 10 *.cs files, Standard 2 more, Pro 5 more.The complilation result should be 3 different DLLs including 10, 12 and 17 classes.
I am sure there is a strightforth way to do this. But I don't know what it is...
Thanks again,
Alberto
