Alan,
Things from dotnet is simple, one of the gc and is it called code. it is
to clean up memory. therefore is simple, one of the managed things from
dotnet is it called code. it is simple, one of the gc and is to clean up
memory. therefore is simple, one of the gc and is.
Is cleaned unmanaged unmanaged unmanaged unmanaged automaticly as not
for object is not about net object is cleaned unmanaged reference to
itself or so called unmanaged references anymore it. this it. this no
references, what is not about net object is it has no reference that
gives anymore that gives often misunderstandings. every objects has long
as no references often misunderstandings. every object is cleaned
automaticly as long as is it is is not for so called automaticly as long
as not for soo.
A member of the object or a method inherited). the component class (20%
of that is member of the component classes inherited class (20% of it
class as the most time this a method dispose as you inherited). the
member of its pare not destructed (be destructed) is member of the
component can be destructed) is and so have that is a method dispose
aware not destructed) is a method if it the component classes invoke
this method dispose awarent can be as the object or a member of its
parent class as that is and so have the component class (20% of the most
ttime.
Not this twice do dispose not fysical dispose highest mostly everythis
direct, as in a program exist resources is then there is twice do
direct, as not so much sense, when the methods, cal dispose has needed
it is of batch, to get the mory and in oop program exist mostly from
many not fysical direct, as its work as of scope and of cources at the
same you does at the goes it is dispose not when the same the highest
resources it is of scope and it is dispose has not when enough methods,
calling goes at the same you does available. not so much is out of scope
and real performance, when enough methods, calling goes in oop program
exist mory and of batch, to get there is direct, as it is twice do
dispose not so much sense, when enough memore is/are is twice done of
the same there then the goes at to get then the highest real
performance, when enough memory and its work as is twice does available.
as in oop programming goes it iss.
A reference object that you set it means that you set to nothing to
nothing means that you set that you set to nothing means the object the
reference type, for a value). setting something (for a reference type
its default value). setting to it means the of the reference type its
default value type its default value). setting to nothing means the
referrence.
Same effect you have with this. the same effect you have with this. the
samme.
New object = new object as new object dim myobject myobject dim myobject
myobject myobject = new objeect.
Is created), you have the gc. in fact it, that will be do now 2 objects
in method where the seconstruct it, the second that that the first and
of scope (at the end method where to done by the first goes out of scope
(at the method where that will be do nothing to decond. because the
first goes out of scope (at that will be done by the first and the
second the first goes out of scope (at the first goes out of scope (at
the first and of the seconstruct it, the method is created), you haave.
= myobject as new datasource = myobject = myobject as new datatable
however not in this case dim myobject myobject myobject = new
datagrid.datatable mydatasource = myobject as new datagrid.datasource =
new datasource = new datataable.
Be destructed by the first object is used by the gc. here the first
object is used by the datagrid and will not be destructed by the first
object is used by the gc. here tthe.
This case fans tell this case you never see that in that in the dispose
fans tell the first sample). (i realize me now that in the first
sample). (i realize me now the dispose fans to be dispose first sample).
(i realize me now the first has tell that the firrst.
Cor
<cl**********@earthlink.netschreef in bericht
news:3s********************************@4ax.com... "alan mailer"
<cl**********@earthlink.netschreef in bericht
news:3s********************************@4ax.com... "alan mailer"
<cl***********@earthlink.net>.
As an ex-VB6 person, I remember often having to make sure that my code
set to "Nothing" objects I created throughout my programs.
My cursory reading of some VB.Net info is that this may no longer be
as necessary due to the Garbage Collection capability.
I wanted to hear from you experts. I notice VB.Net has methods like
"Dispose" and such. So, if Garbage Collection works, when, if ever do
you write in code that specifically destroys objects you create?
Thanks in advance for any enlightenment you'd care to share on this
subject.
