J
Jason
I read there is no difference between calling Close vs. Dispose on
Connection objects.
Is this true?
Connection objects.
Is this true?
S
Sahil Malik
That ain't true.
- Sahil Malik
You can reach me thru my blog at
http://www.dotnetjunkies.com/weblog/sahilmalik
- Sahil Malik
You can reach me thru my blog at
http://www.dotnetjunkies.com/weblog/sahilmalik
W
William \(Bill\) Vaughn
Dispose closes the connection and discards the object. It has no further
effect. It does not impact the connection pool.
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
effect. It does not impact the connection pool.
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
C
Chris Lyon [MSFT]
Bill,
Dispose does not "discard the object".
See http://weblogs.asp.net/clyon/archive/2004/09/21/232445.aspx
Close() and Dispose() should be equivalent. See http://msdn.microsoft.com/library/d.../en-us/cpgenref/html/cpconfinalizedispose.asp for more information.
-Chris
--------------------
--
This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
Dispose does not "discard the object".
See http://weblogs.asp.net/clyon/archive/2004/09/21/232445.aspx
Close() and Dispose() should be equivalent. See http://msdn.microsoft.com/library/d.../en-us/cpgenref/html/cpconfinalizedispose.asp for more information.
-Chris
--------------------
--
This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
W
William \(Bill\) Vaughn
Okay, let me rephrase. Once you call Dispose, you can't use the object's
properties or methods. The object remains in memory until the GC flushes its
memory... but it's "discarded" as far as your code is concerned. Close
simply marks the connection as reusable (in the pool) and you can
subsequently inspect Connection properties and use the Open method again.
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
properties or methods. The object remains in memory until the GC flushes its
memory... but it's "discarded" as far as your code is concerned. Close
simply marks the connection as reusable (in the pool) and you can
subsequently inspect Connection properties and use the Open method again.
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"Chris Lyon [MSFT]" said:
C
Chris Lyon [MSFT]
Bill,
Calling Dispose() doesn't then prohibit you from calling the object's properties and methods. See this blog post, in particular the comments:
http://weblogs.asp.net/clyon/archive/2004/09/23/233464.aspx
If the class' developer followed the Dispose Pattern (link below) correctly, then Close and Dispose are equivalent.
For example, a SQLConnection object will have the same behaviour after calling Close or Dispose. The same InvalidOperationExceptions will be thrown when some methods
(like ChangeDatabase()) are called, but not all.
-Chris
--------------------
--
This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
Calling Dispose() doesn't then prohibit you from calling the object's properties and methods. See this blog post, in particular the comments:
http://weblogs.asp.net/clyon/archive/2004/09/23/233464.aspx
If the class' developer followed the Dispose Pattern (link below) correctly, then Close and Dispose are equivalent.
For example, a SQLConnection object will have the same behaviour after calling Close or Dispose. The same InvalidOperationExceptions will be thrown when some methods
(like ChangeDatabase()) are called, but not all.
-Chris
--------------------
--
This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
S
Sahil Malik
Chris,
Here is reflected code out of SqlConnection.Dispose ---
protected override void Dispose(bool disposing)
{
switch (this._objectState)
{
case ConnectionState.Open:
{
goto Label_0017;
}
}
goto Label_0035;
Label_0017:
if (disposing)
{
this.Close();
this._connectionOptions = null;
this._cachedOptions = null;
this._connectionString = null;
}
Label_0035:
base.Dispose(disposing);
}
You can clearly see Dispose does more than Close, it sets certain properties
to null. .. therefore Dispose is not the same as Close.
I think Bill's right dude :-/
- Sahil Malik
You can reach me thru my blog at
http://www.dotnetjunkies.com/weblog/sahilmalik
thrown when some methods
originated.
Here is reflected code out of SqlConnection.Dispose ---
protected override void Dispose(bool disposing)
{
switch (this._objectState)
{
case ConnectionState.Open:
{
goto Label_0017;
}
}
goto Label_0035;
Label_0017:
if (disposing)
{
this.Close();
this._connectionOptions = null;
this._cachedOptions = null;
this._connectionString = null;
}
Label_0035:
base.Dispose(disposing);
}
You can clearly see Dispose does more than Close, it sets certain properties
to null. .. therefore Dispose is not the same as Close.
I think Bill's right dude :-/
- Sahil Malik
You can reach me thru my blog at
http://www.dotnetjunkies.com/weblog/sahilmalik
properties and methods. See this blog post, in particular the comments:"Chris Lyon [MSFT]" said:
correctly, then Close and Dispose are equivalent.
calling Close or Dispose. The same InvalidOperationExceptions will be
thrown when some methods
rights. Use of included script samples are subject to the terms specified at
message are best directed to the newsgroup/thread from which they
originated.
W
William \(Bill\) Vaughn
I stand corrected. When I saw that my opens failed post dispose I took it to
mean the object was missing--it was simply cleared. Learn something new
every day. Thanks
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
mean the object was missing--it was simply cleared. Learn something new
every day. Thanks
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"Chris Lyon [MSFT]" said:
C
Chris Lyon [MSFT]
Hm. Interesting.
According to the Dispose Pattern, Close should call Dispose. It looks like in this case a little more cleanup is happening. I'm not familiar enough with SQLConnection to know
what kind of effects this might have on your object, or whether it's appropriate to continue to use a SQLConnection object after it's been closed.
Close and Dispose are equivalent, in the sense that when you're done with a connection object, calling either Close or Dispose is sufficient to free your unmanaged resource.
-Chris
--------------------
--
This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
According to the Dispose Pattern, Close should call Dispose. It looks like in this case a little more cleanup is happening. I'm not familiar enough with SQLConnection to know
what kind of effects this might have on your object, or whether it's appropriate to continue to use a SQLConnection object after it's been closed.
Close and Dispose are equivalent, in the sense that when you're done with a connection object, calling either Close or Dispose is sufficient to free your unmanaged resource.
-Chris
--------------------
--
This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
S
Sahil Malik
Close and Dispose are equivalent, in the sense that when you're done with
a connection object, calling either Close or Dispose is sufficient to free
your unmanaged resource.
That I totally agree with
... havagudday !! (me leavin' work will be in
dotnetrocks tonight - chatroom .. see ya there).
- Sahil Malik
You can reach me thru my blog at
http://www.dotnetjunkies.com/weblog/sahilmalik
enough with SQLConnection to know
closed.
your unmanaged resource.
originated.
a connection object, calling either Close or Dispose is sufficient to free
your unmanaged resource.
That I totally agree with
... havagudday !! (me leavin' work will be indotnetrocks tonight - chatroom .. see ya there).
- Sahil Malik
You can reach me thru my blog at
http://www.dotnetjunkies.com/weblog/sahilmalik
like in this case a little more cleanup is happening. I'm not familiar"Chris Lyon [MSFT]" said:
enough with SQLConnection to know
appropriate to continue to use a SQLConnection object after it's been
closed.
a connection object, calling either Close or Dispose is sufficient to free
your unmanaged resource.
rights. Use of included script samples are subject to the terms specified at
message are best directed to the newsgroup/thread from which they
originated.