Hi Jenny,
"Jenny" <an*******@discussions.microsoft.com> wrote in message
news:00****************************@phx.gbl...
After running for 8 hours, our n-tier DB program (written
in VB.NET) gradually grows from 50MB to 561MB in size. It
slowly grinds to a halt & the end user has to restart the
application. Is there a way to explicitely call the
garbarge collector? I previously developed in C++ & had
to call New[] and delete[].
This memory mgt instability in .NET is not acceptable.
Howver, porting to Java isn't an option at this time.
I think you're being hasty blaming this on .NET "memory mgt
instability". There are some things that must be taken into account in a
distributed app that, if ignored, could result in your app "leaking". Does
your middle tier use COM+ component services (i.e. do you have middle tier
"service" objects that inherit from ServicedComponent)? If so, the client
should "dispose" of those objects when it is done with them, or (a better
option, IMHO) make your "service" objects JIT activated (see the
JustInTimeActivation attribute).
Regards,
Dan