When you start .NET application there a more code loaded in the process
beside the lines that you wrote. The process host .NET CLR, framework
libraries.... It allocates memory for the managed heap, etc. Why yout so
worried about the memory consumption? Unless you write programs for small
devices and with nowadays hardware 10M should be out of any concerns.

Signature
Stoitcho Goutsev (100) [C# MVP]
> When I create a winform app (even with no additional code or controls), it
> typically takes 7 - 10Mb on startup. An app with 3 forms can take 3x
[quoted text clipped - 6 lines]
> I do not want the user to have to minimize the form manually or watch the
> form minimize then reappear.
DotNet - 01 Oct 2004 20:11 GMT
I appreciate your response.
I understand that there are .NET CLR components being loaded on startup.
But why does so much space get allocated and then freed up on minimize? I
would then expect returning the windowstate to normal would reallocate the
space, but it does not.
The primary concern is acceptance from the organizations's architecture and
desktop services teams. They do not want to deploy an application that
appears to be very resource intensive compared to the functionality. And it
is difficult to explain why the memory is freed up on a minimize, and then
not reallocated on a restore. They will not accept the explanation that this
is just the way that .NET works. Is there no method to constrain resource
consumption, or better manage it?
"Stoitcho Goutsev (100) [C# MVP]" wrote:
> When you start .NET application there a more code loaded in the process
> beside the lines that you wrote. The process host .NET CLR, framework
[quoted text clipped - 12 lines]
> > I do not want the user to have to minimize the form manually or watch the
> > form minimize then reappear.