There are a few minor places where code for my project may be able to be drastically improved if the target framework were a newer version. I’d like to be able to better leverage conditional compilation in C# to switch these as needed.
Something like:
#if NET40
using FooXX = Foo40;
#elif NET35
using FooXX = Foo35;
#else NET20
using FooXX = Foo20;
#endif
Do any of these symbols come for free? Do I need to inject these symbols as part of the project configuration? It seems easy enough to do since I’ll know which framework is being targeted from MSBuild.
/p:DefineConstants="NET40"
How are people handling this situation? Are you creating different configurations? Are you passing in the constants via the command line?
One of the best ways to accomplish this is to create different build configurations in your project:
And in one of your default configurations:
Which would set the default if it wasn’t defined anywhere else. In the above case the OutputPath will give you a separate assembly each time you build each version.
Then create a AfterBuild target to compile your different versions:
This example will recompile the entire project with the Framework variable set to NET20 after the first build (compiling both and assuming that the first build was the default NET35 from above). Each compile will have the conditional define values set correctly.
In this manner you can even exclude certain files in the project file if you want w/o having to #ifdef the files:
or even references