Even targeting 3.5, metadata version v2.0.50727 ?
-
Just a matter of curiosity and general knowledge..easy question it seems but I didn't find an answer :( My project (I'm using VS2008) targets .net framework 3.5, but after compiling the IDLASM shows: // Metadata version: v2.0.50727 and examining the loaded application, the used DLLs really points to the 2.05 framework...should'nt it target the 3.5 ? Thanks for any help
GuimaSun www.nexsun.com.br NEXSUN TechZone
-
Just a matter of curiosity and general knowledge..easy question it seems but I didn't find an answer :( My project (I'm using VS2008) targets .net framework 3.5, but after compiling the IDLASM shows: // Metadata version: v2.0.50727 and examining the loaded application, the used DLLs really points to the 2.05 framework...should'nt it target the 3.5 ? Thanks for any help
GuimaSun www.nexsun.com.br NEXSUN TechZone
It is targetting 3.5. .NET 2.0, 3.0 and 3.5 all use the .NET 2.0 CLR. .NET 3.0 and 3.5 are just set of extensions to the .NET Framework Class Libraries. Neither of them introduced any additional functionality to the .NET CLR.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008 -
It is targetting 3.5. .NET 2.0, 3.0 and 3.5 all use the .NET 2.0 CLR. .NET 3.0 and 3.5 are just set of extensions to the .NET Framework Class Libraries. Neither of them introduced any additional functionality to the .NET CLR.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008This is the answer I thought I'd get, but I found many articles refering to this as the required framework version. So, how can I get the required framework from the assembly file ? Thanks a lot.
GuimaSun www.nexsun.com.br NEXSUN TechZone
-
This is the answer I thought I'd get, but I found many articles refering to this as the required framework version. So, how can I get the required framework from the assembly file ? Thanks a lot.
GuimaSun www.nexsun.com.br NEXSUN TechZone
The line you're look at is telling you the .NET CLR version that is required to execute the code, not the .NET Framework version. The CLR is the virtual machine runtime that executes the code. The Framework is the class library that supplies the functionality for the thousands of classes you can use in your code. There is nothing in the metadata that specifies the .NET Framework version that is required to run the app. What you see in the manifest is the required .NET CLR version. Under that, you'll see a bunch of
.assembly externreferences. Each of these imports a namespace, specifying the public key and VERSION NUMBER the loader must bind to. Each reference can have it's own version number seperate from the rest. For example, if you create a blank WPF app targeting .NET Framework 3.5, you see the MSCORLIB is version 2.0, from .NET 2.0, SYSTEM from .NET 2.0, PresentationFramework from .NET 3.0, and WindowBase from .NET 3.0.A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008