Hey

I don't think this is possible but thought I'd just double check...

I have a class library project (i.e building this project results in a DLL being created) and I add a reference to this DLL in several of my other applications. This DLL project targets .NET Framework v2.0.

However, some of these apps that use the DLL target .NET 2.0 (or 3.5) and some target .NET 4.0. But because .NET 4.0 does not include 2.0 and 3.5 in it, its possible for someone to have .NET 4.0 installed but not .NET 2.0, therefore meaning that they won't be able to run my app because of the reference to a DLL that requires .NET 2.0.

So the solutions as far as I can see are:
1. Include .NET 2.0/3.5 as an additional prereq for my .NET 4.0 apps... ewww.
2. Create a copy of this DLL project and make it target .NET 4.0 then in my .NET 4.0 apps add a reference to that rather than the .NET 2.0 version.

So far I've been using the second option, which is working fine but its just very annoying having to remember to copy and paste any changes I make in one version of the DLL project into the other one.

So is there any way I can have a single DLL project but have it build 2 versions of the DLL, one targeting .NET 2.0/3.5 and one targeting .NET 4.0?
As I've written this down I've just realised I could always build the solution, copy the DLL out to another folder, then change the target framework and build it again to get the new DLL but that's still not ideal.


Using VS 2010 Ultimate by the way in case that makes any difference to the options I've got available

Thanks
Chris