Properly disposing of a DbConnection?
Call connection.Dispose() from within your dispose method. You should look at the standard pattern for implementing IDisposable, which goes above and beyond simply implementing the IDisposable interface and allows for disposing unmanaged objects etc: public void Dispose() { Dispose(true); GC. SuppressFinalize(this); } protected virtual void Dispose(bool disposing) { if (!disposed) { if (disposing) { // Dispose managed resources.
} // There are no unmanaged resources to release, but // if we add them, they need to be released here. } disposed = true; // If it is available, make the call to the // base class's Dispose(Boolean) method base. Dispose(disposing); } (Taken from http://msdn.microsoft.com/en-us/library/system.idisposable.aspx ).
Call connection.Dispose() from within your dispose method. You should look at the standard pattern for implementing IDisposable, which goes above and beyond simply implementing the IDisposable interface and allows for disposing unmanaged objects etc: public void Dispose() { Dispose(true); GC. SuppressFinalize(this); } protected virtual void Dispose(bool disposing) { if (!disposed) { if (disposing) { // Dispose managed resources.
} // There are no unmanaged resources to release, but // if we add them, they need to be released here. } disposed = true; // If it is available, make the call to the // base class's Dispose(Boolean) method base. Dispose(disposing); } (Taken from http://msdn.microsoft.com/en-us/library/system.idisposable.aspx).
My 2 cents: DB connection is unmanaged resource. – Darius Kucinskas Mar 1 at 10:45.
According to this newsgroup: Here is how IDbConnection.Dispose() is implemented (as Reflector utility shows): SqlClient: protected override void Dispose(bool disposing) { if (disposing) { switch (this. _objectState) { case ConnectionState. Open: { this.Close(); break; } } this.
_constr = null; } base. Dispose(disposing); } Odbc: protected override void Dispose(bool disposing) { if (disposing) { this. _constr = null; this.Close(); CNativeBuffer buffer1 = this.
_buffer; if (buffer1! = null) { buffer1.Dispose(); this. _buffer = null; } } base.
Dispose(disposing); } OleDb: protected override void Dispose(bool disposing) { if (disposing) { if (this. ObjectState! = 0) { this.DisposeManaged(); if (base.
DesignMode) { OleDbConnection. ReleaseObjectPool(); } this. OnStateChange(ConnectionState.
Open, ConnectionState. Closed); } if (this. PropertyIDSet!
= null) { this.propertyIDSet.Dispose(); this. PropertyIDSet = null; } this. _constr = null; } base.
Dispose(disposing); } Your dispose method should only attempt to close the connection if it is open.
Just to complete the IDisposable implementation pattern, it's convention to include a finalizer (destructor) for your class which calls the Dispose() method (passing false). This acts as a failsafe mechanism, allowing you to dispose of unmanaged objects if the consumer of the class fails to call Dispose(). ~MyClass() { Dispose(false); }.
I have a class called DatabaseHelper that wraps a DbConnection. What's the proper way to setup this class for a using statement? I have implemented IDisposible, but I'm not sure when and where I should be calling Connection.Close() or Connection.Dispose().
When I simply call Connection.Dispose() in my own Dispose() method, I'll sometimes get a SocketException from my DbConnection object. I assume this is because old connections are being left open, but there's no details attached the to exception, so I can't know for sure.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.