1

I have a project that is currently building in .NET 3.5 (CLR 2.0), and I want to upgrade to .NET 4.0 (CLR 4.0), but there are folks dependent on my project that are going to be loading the DLL in a 2.0 process.

So I'm thinking of using the MSBuild task to make two copies of my dlls, one for CLR 2.0 and one for CLR 4.0.

Any other good suggestions?

Guruprasad Nilam
  • 33
  • 2
  • 1
    Hmm, trying to solve people-problems with build-settings. That's been known to not work. Make a compelling case to the boss, ask how to do that at programmers. – Hans Passant Jul 09 '11 at 22:33
  • 2
    Since you'd be constrained to .NET 3.5 features anyway, what benefit do you expect from having a .NET 4 version? – Thomas Gerstendörfer Jul 10 '11 at 11:42
  • You can look at setting the targetRuntime in the assembly. Did you look at the useLegacyV2RuntimeActivationPolicy.. Take a look:http://stackoverflow.com/questions/1604663/what-does-uselegacyv2runtimeactivationpolicy-do-in-the-net-4-config – sajoshi Jul 14 '11 at 09:52

0 Answers0