Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve a solution targeting .net framework 3.5. All the references to core dlls have runtime version 2.x since they were compiled with it. Why is it so? Does this mean I’m not using latest versions of those DLLs with bug-fixes?
Framework 3.5 is still working on the CLR 2.0. The V3 and V3.5 only added some (a lot in fact) new classes, but didn’t changed the existing assemblies. The compiler has also changed, but in fact, not the runtime.
That’s why in
%windir%\Microsoft.NET\Framework\v3.5(or Framwork64), you won’t find the assemblies already available in the V2.The Framework V4 has introduced a new version of the CLR. You’ll find accordingly in
%windir%\Microsoft.NET\Framework\v4.0.30319all assemblies.The Versions and Dependencies page list all versions, both base class library version and clr version.
[Edit] As the V4.5 is coming soon, the same table is available for the next version.