Sorry no, that would take one of the core designers and developers. We forum volunteers aren't privy to that kind of detailed inside information.It's a more general question. I'm just curious, but if you can explain me this issue I'll be very grateful.
.NET applications using the 2.0 CLR (.NET 3.5, .NET 3) can't run on .NET 4 automatically.
The easier solution is of course to have .NET 3.5 installed as well then the application will automatically pick the correct CLR to run the .NET app. There is however a way to enable CLR 2.0 applications on just the .NET 4.0 runtime, it requires a app.config (myexefilename.exe.config) with a compatibility setting enabled. Some quick googling found this, I have it working on one of my apps but I can't remember if this is correct.
<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0" />
</startup>
</configuration>
Here's the compatibility page for .NET if you want more.
http://msdn.microsoft.com/en-us/library/ff602939.aspx
Sorry no, that would take one of the core designers and developers. We forum volunteers aren't privy to that kind of detailed inside information.
.NET applications using the 2.0 CLR (.NET 3.5, .NET 2) can't run on .NET 4 automatically.
The easier solution is of course to have .NET 3.5 installed as well then the application will automatically pick the correct CLR to run the .NET app. There is however a way to enable CLR 2.0 applications on just the .NET 4.0 runtime, it requires a app.config (myexefilename.exe.config) with a compatibility setting enabled. Some quick googling found this, I have it working on one of my apps but I can't remember if this is correct.