B
Bob
Hi,
In VS2003 conditional compilation constants and their state could be defined
at project level.
I was using this to control what features where offered by various builds.
i.e. Feature1=true,Feature2=false, ...
VS2005 seems to either allow the existance of the constant or not.
ie. You must omit a constant not declare it to be false
This means that the list no longer declares the state of all the options.
So...
I think that perhaps I am not using the right tool for the job.
What is the 'correct' way to control conditional compilation at project
level?
Thanks
Bob
In VS2003 conditional compilation constants and their state could be defined
at project level.
I was using this to control what features where offered by various builds.
i.e. Feature1=true,Feature2=false, ...
VS2005 seems to either allow the existance of the constant or not.
ie. You must omit a constant not declare it to be false
This means that the list no longer declares the state of all the options.
So...
I think that perhaps I am not using the right tool for the job.
What is the 'correct' way to control conditional compilation at project
level?
Thanks
Bob