I have built a class library that I've initially written in Visual Studio 2010 using .NET 4.0 features, including the new TPL classes.
However, I would also like to publish a Visual Studio 2008 compatible version of the class library, built for .NET 3.5 (2.0), without the specific features related to .NET 4.0.
My question is this: How would I best set up this so that I can easily fix bugs and get bugfixes in both versions, as long as it is in common code?
Here's the various ways I've discovered:
- Create a whole 'nother repository for the .NET 3.5 version, manually merge bugfixes over (ie. they're not really related through Kiln, just me manually copying changes over using Beyond Compare or a similar tool)
- Creating a branch, and keeping two branches open
- Named branch (what's the difference between a named branch and an unnamed one?)
- Creating a sub-repository (what is this?)
As you can see, I have plenty of questions, any guidance you can give me at all would be most welcome, but most of all, if anyone has already done what I'm trying to do, any specific pointers as to what worked best would be most welcome.
Things that I need to handle:
- Project files and Solution file has different format, so either I:
- Create unique names for those, and just keep everything together
- or, branch/split (see questions above)
- Some changes internally in the files, mainly to remove support for TPL-classes (.NET 4.0) in the Visual Studio 2008 (.NET 3.5) version, I can do this using #if DOTNET40 type of defines easily, but if it's better to branch and make the changes, then I'd like to know that (I assume not.)