excessive memory usage in VS.NET ?

[zeflash]

When I first open my solution (containing around 500 files / classes in 8 projects), devenv takes roughly 35 megs of RAM & virtual memory.
But at some point it rockets up to 115 MB of VM, without any apparent reason.

I know that RAM is cheap these days, but isn't 115 MB a bit extreme ? it's only a UI !
Compared to VC6 which takes at most 30 MB of VM (with visual assist) it's quite a leap.

[Mike Pliam]

I too have been dismayed at the size of the executables produced using C++.NET, compared to those using the very same source code produced using VCPP 6.0.

For example, a rather simple dialog-based MFC program with MFC library statically linked to the executable yields programs of the following sizes with the two compilers:


VCPP 6.0 C++.NET

Debug 1349 kb 1880 kb

Release 132 kb 224 kb

which is roughly 72 and 60 percent larger using C++.NET.

Now Microsoft's documentation states that the 'Standard Edition' does not contain the optimized compiler which is only available by purchasing the entire Visual Studio .NET suite of compilers and applications. In other words, the 'Professional Edition' which does contain compiler optimization cannot, at the present time, be purchased as a single item. So if your only interested in compiling using C++ and dont give a hoot about C# and all the other rigamorole, your screwed.

Unless you simply wish to stick with VCPP 6.0 which most of us found to be quite a nice compiler. But that is not really an option. If you go out to try and purchase VCPP 6.0 today, you will not find it on most software distributors shelves. Reason -- Microsoft recalled all the older softer and replaced it with .NET stuff.

Perhaps it's time to start thinking about other compilers.

Mike