framework 3.5 folder looks short

[Francesco Sozzi]

I've just installed VS 2008 and I discovered that Framework 3.5 folder
(C:\WINDOWS\Microsoft.NET\Framework\v3.5 ) is very short if compared to
prevoious versions (26.4 MB for 3.5 vs 164MB for 2.0). It has very few files
and all assemblies seem to stay into Compact Framework folder instead
(C:\Program Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE ).
Is it right?...

Does it mean that on VS 2008 I have to put into references assemblies from
Compact Framework?

 

[Jon Skeet [C# MVP]]

I've just installed VS 2008 and I discovered that Framework 3.5 folder
(C:\WINDOWS\Microsoft.NET\Framework\v3.5 ) is very short if compared to
prevoious versions (26.4 MB for 3.5 vs 164MB for 2.0). It has very few files
and all assemblies seem to stay into Compact Framework folder instead
(C:\Program Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE ).
Is it right?...

The assemblies are in C:\Program Files\Reference Assemblies\Microsoft
\Framework\v3.5

Bear in mind that 3.5 is just a set of assemblies on top of .NET 3.0,
along with some new language compilers etc. (In turn .NET 3.0 is a set
of assemblies on top of .NET 2.0 - they all use the same CLR.)

Does it mean that on VS 2008 I have to put into references assemblies from
Compact Framework?

No, see above. (You shouldn't be adding references to system
assemblies via directories anyway - just use the version in the GAC.)

Jon

 

[Francesco Sozzi]

Hi Jon,

Thanks for answer.

Is it also true for 2.0 or this one replace 1.1?

Francesco

 

[Jon Skeet [C# MVP]]

Thanks for answer.

Is it also true for 2.0 or this one replace 1.1?

2.0 actually upgraded assemblies rather than just adding new ones, and
you can run 2.0 without 1.1 (whereas you can't run 3.5 without 2.0).

Jon

 

[Francesco Sozzi]

ok, thanks
Francesco

2.0 actually upgraded assemblies rather than just adding new ones, and
you can run 2.0 without 1.1 (whereas you can't run 3.5 without 2.0).

Jon