Databases
StackOverflow2013
Postsdbo
PODealing with .NET IDisposable objects
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODealing with .NET IDisposable objects
    primarykey
    data
    text
    <p>I work in C#, and I've been pretty lax about using <code>using</code> blocks to declare objects that implement <code>IDisposable</code>, which you're apparently always supposed to do. However, I don't see an easy way of knowing when I'm slipping up. Visual Studio doesn't seem to indicate this in any way (am I just missing something?). Am I just supposed to check help every time I declare anything, and gradually build up an encyclopedic memory for which objects are and which are not disposable? Seems unnecessary, painful, and error-prone.</p> <p>How do <em>you</em> handle this?</p> <p><strong>EDIT:</strong></p> <p>Looking at the related questions sidebar, I found <a href="https://stackoverflow.com/questions/2785/setting-objects-to-nullnothing-after-use-in-dot-net">another question</a> which made it clear that <code>Dispose()</code> is supposed to be called by the object's finalizer anyway. So even if you never call it yourself, it should eventually happen, meaning you won't have a memory leak if you don't use <code>using</code> (which is what I suppose I was really worried about all along). The only caveat is that the garbage collector doesn't know how much extra memory is being held by the object as unmanaged stuff, so it won't have an accurate idea how much memory will be freed by collecting the object. This will result in less-ideal-than-usual performance by the garbage collector.</p> <p>In short, it's not the end of the world if I miss a <code>using</code>. I just wish something would generate at least a warning for it.</p> <p>(Off-topic: why is there no special markdown for linking to another question?)</p> <p><strong>EDIT:</strong></p> <p>Ok, fine, stop clamoring. It's super duper all-fired <a href="http://www.youtube.com/watch?v=a1Y73sPHKxw" rel="nofollow noreferrer">dramatic-chipmunk</a>-level <strong><em>important</em></strong> to call <code>Dispose()</code> or we'll all <em>die</em>.</p> <p>Now. Given that, why is it so easy &mdash; hell, why is it even <em>allowed</em> &mdash; to do it wrong? You have to go out of your way to do it right. Doing it like everything else results in armageddon (apparently). So much for encapsulation, huh?</p> <p>[Stalks off, disgusted]</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USAtario
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODealing with .NET IDisposable objects
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODealing with .NET IDisposable objects
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PODealing with .NET IDisposable objects
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYou won't find a single experienced .net programmer on the planet that will agree with you. I don't mean to be melodramatic, but you really should pick up a good .Net book.
      singulars
      1. PODealing with .NET IDisposable objects
      1. USJason Jackson
    2. CO@Atario - you really should consider changing the accepted answer; frankly, Timwi is wrong - or at best, vastly over-simplifying things to the point where the two (wrong vs simplified) are very close.
      singulars
      1. PODealing with .NET IDisposable objects
      1. USMarc Gravell
    3. COYou should call dispose as soon as you can, because it could release resources long before the next garbage collection is done. If an object is using a resource on your server or desktop that would be released by Dispose(), do you really want to wait for the garbage collector to get around to it?
      singulars
      1. PODealing with .NET IDisposable objects
      1. USJason Jackson
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload