3.5 is set on top of 2.0, so it is not loading entire frameworks 2.0 and
3.5. Furthermore, the framework is sliced up into different assemblies,
which are divided into classes. Portions of this framework are ngened, while
other portions are not.
What this means to you is the only thing loaded is that which you are using,
so don't sweat it.
As far as memory, .NET "eats" a lot of memory anyway. This sounds bad, but
it is really rather efficient overall, as it only garbage collects when it
needs memory. On your machine, you will see this as a growing footprint
until it reaches a certain size. Most of the "used" memory is actually ready
to be collected, but .NET waits until it is needed. "Used" memory that is
not actively being much like "unused" memory, except it needs to be marked
so the rest of the system can take advantage of it.
Hope this helps. Probably a bit too meandering.
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
Subscribe to my blog
http://gregorybeamer.spaces.live.com/lists/feed.rss
*************************************************
| Think outside the box!
|
*************************************************