"forcing" garbage collection

[Jon Mcleod]

I'm trying to wrap my ming around C#/CLR garbage collection. In an
ASP.NET project, I'm having a problem because an object destructor is
being called by another thread, long after my code is done. I'm wanting
to know if I can force it to happen immediately (when the object goes
out of scope) without going back and adding all of the required
Dispose() calls..

public Method()
{
CustomClass o = new CustomClass(..) ;
..
..
..
};

Is there a way to "force" the CustomClass destructor to be called right
when the object goes out of scope, by the same thread as the Method?

Thanks.

[=?UTF-8?B?QXJuZSBWYWpow7hq?=]

First, at some point every non-memory resource in dotNET is a OS

resource and closing it when done is a good thing to do.

Yes !

So Close/Dispose those.

The real problem on whether or not to use dispose is that the framework
has blurred the lines between managed and unmanaged. For someone who
has never written to the underlying OS, the fact that a lot of the
framework classes contains a Dispose method really doesn't have any
meaning because the non-memory OS resource is "hidden" from them.

If something implements IDisposable, then you can just call Dispose.

If it is a no-op then the overhead is very small.

Better safe than sorry.

Arne

[=?ISO-8859-1?Q?Arne_Vajh=F8j?=]

Jon Mcleod wrote:

In this case, the object is a managed object but it contains a database
connection. This is an ASP.NET project, and there are two problems.
First, these objects are being left alive for quite some time, causing
the site to start artificially running out of database connections after
running a while. Secondly, GC happens on its own thread, causing a
"Internal .Net Framework Data Provider error 1." when it calls Close on
the the apparently single-threaded SqlConnection object.

My solution right now it to use IDisposed to explicitly manage the
lifetime of these objects, to sidestep the whole issue. I don't have a
lot of experience with these technologies, though. Is there a better way?

database =call Close or Dispose

If not then you will get problems !

Arne