Dataset dispose

[Agnes]

Does dataset dispose will lead the related dataadpator , or database will
dispose also ?
Or I need to dispose them one by one ??

[Brian Gideon]

On Apr 20, 4:56 am, "Agnes" <[e-mail]:

Does dataset dispose will lead the related dataadpator , or database will
dispose also ?
Or I need to dispose them one by one ??

You do not need to call Dispose on a DataSet. It's one of the few
exceptions to the rule that you should call Dispose when you're
finished using an object. It is recommended that you continue calling
Dispose on connection and data adapter objects though.

And no, calling Dispose on a DataSet will not dispose anything else.

[Larry Linson]

you don't need to call .Dispose on anythnig

if the objects don't clean up after themselves then call up M$ tech
support

THIS CRAP IS NEITHER VISUAL NOR BASIC

On Apr 20, 7:56 am, Brian Gideon <[e-mail]:

On Apr 20, 4:56 am, "Agnes" <[e-mail]:

Does dataset dispose will lead the related dataadpator , or database will
dispose also ?
Or I need to dispose them one by one ??

You do not need to call Dispose on a DataSet. It's one of the few
exceptions to the rule that you should call Dispose when you're
finished using an object. It is recommended that you continue calling
Dispose on connection and data adapter objects though.

And no, calling Dispose on a DataSet will not dispose anything else.

[Brian Gideon]

On Apr 20, 9:58 am, Larry Linson <[e-mail]:

you don't need to call .Dispose on anythnig

if the objects don't clean up after themselves then call up M$ tech
support

THIS CRAP IS NEITHER VISUAL NOR BASIC

You don't *have* to call Dispose (or Close). In the case of an
IDbConnnection the GC will eventually clean it up, but until it does
you'll have a dangling connection that remains open.

[Herfried K. Wagner [MVP]]

"Larry Linson" <la***********@hotmail.comschrieb:

you don't need to call .Dispose on anythnig

That's true ("need" interpreted in the sense of "it's not necessary, but it
may cause the application to refuse to work properly"), but this doesn't
mean that it doesn't make sense to prevent the application from running out
of unmanaged resources (connections, file handles, ...).

I suggest to call 'Dispose' on every object that provides the method,
because alternative implementations of the .NET Framework may place code
there to free unmanaged resources.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>

[Cor Ligthert [MVP]]

I suggest to call 'Dispose' on every object that provides the method,

But don't do it myself.
You can look at my website you don't see any Textbox.dispose, label.dispose,
etc.

>

Written for M S Herfried K. Wagner. I hope he likes it I did some work
for him.

Cor

[Brian Gideon]

On Apr 23, 1:39 pm, "Cor Ligthert [MVP]" <[e-mail]>
wrote:

I suggest to call 'Dispose' on every object that provides the method,

But don't do it myself.
You can look at my website you don't see any Textbox.dispose, label.dispose,
etc.

Those are eventually called through the Control.Dispose implementation
of the containing Form.

[Herfried K. Wagner [MVP]]

"Brian Gideon" <br*********@yahoo.comschrieb:

I suggest to call 'Dispose' on every object that provides the method,

But don't do it myself.
You can look at my website you don't see any Textbox.dispose,
label.dispose,
etc.

Those are eventually called through the Control.Dispose implementation
of the containing Form.

Right.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>

[Cor Ligthert [MVP]]

Brian,

You would not believe it, I know that already some time.
But therefore Herfrieds advise is even more wrong if you know that..

Cor

"Brian Gideon" <br*********@yahoo.comschreef in bericht
news:11**********************@y5g2000hsa.googlegro ups.com...

On Apr 23, 1:39 pm, "Cor Ligthert [MVP]" <[e-mail]>
wrote:

I suggest to call 'Dispose' on every object that provides the method,

But don't do it myself.
You can look at my website you don't see any Textbox.dispose,
label.dispose,
etc.

Those are eventually called through the Control.Dispose implementation
of the containing Form.

[Herfried K. Wagner [MVP]]

"Cor Ligthert [MVP]" <no************@planet.nlschrieb:

You would not believe it, I know that already some time.
But therefore Herfrieds advise is even more wrong if you know that..

Well, I should have written: "I suggest to make sure 'Dispose' is called on
every object implementing 'IDisposable' when the object is not needed any
more."

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>

[Cor Ligthert [MVP]]

For sure that is a fine text in my idea completely as it has to be.

But also for by instance members from the namespace System.Data.

Where the team has taken the action to dispose if it is needed after every
close.

Cor

"Herfried K. Wagner [MVP]" <hi***************@gmx.atschreef in bericht
news:eX**************@TK2MSFTNGP04.phx.gbl...

"Cor Ligthert [MVP]" <no************@planet.nlschrieb:

>You would not believe it, I know that already some time.
But therefore Herfrieds advise is even more wrong if you know that..

Well, I should have written: "I suggest to make sure 'Dispose' is called
on every object implementing 'IDisposable' when the object is not needed
any more."

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>