VB.Net-made app consumes more memory than VB6.0-made ones?

[dee-u]

It seems to be the case unless proven wrong by others...

[Merrion]

No - this is the case but it is handy to know why.

When you start a .NET application it allocates a big heap of memory for its own use and the framework memory handling system (also the "garbage collection") works with this.

When you work in VB6 the app grows the heap each time you need more memory.

Since heap management takes clock cycles, the .NET designers have traded memory footprint for speed (and stability).

The analogy is like if you are building a wall. The .NET way is to order a palette of bricks (which takes up space on your driveway) and take from the palette as the wall is built - only getting another palette if the current one runs out whereas the VB6 way is to go to the store for each brick in turn.