I need to create some core libraries within my application which will be available in both .NET 3.5 and .NET 4.0. I'm happy creating multiple projects, creating the required defines and using #ifdef
to control which code make it into which output assembly.
However, what I would like to know is if there is a way of keeping those projects in sync? When I am developing under XNA, I have a Windows build and a Windows Phone build - and XNA injects a property into the project file called XnaCrossPlatformGroupID
. What it does with that is enable Visual Studio to automagically make sure that when a file is added to a project, it is added to the corresponding project. So, for example, if I add a file called Foo.cs
to the Windows copy of my project, then that same file is added to the Windows Phone copy of the project.
Is there any way of replicating that sort of behaviour for a normal set of projects within Visual Studio? I would prefer not to use build configurations, as I would like to be able to compile all targeted platforms in a single step, without resorting to tools outside of the IDE (something like TeamCity, for instance). Or is there another method that allows a project to be built against multiple targets without peppering the solution with 20 different build configurations?
See Question&Answers more detail:
os 与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…