If you are using .NET Framework 4.5 or later, there is a StreamWriter overload using which you can ask the base stream to be left open when the writer is closed. In earlier versions of .NET Framework prior to 4.5, StreamWriter assumes it owns the stream. Options: Don’t dispose the StreamWriter; just flush it. Create … Read more
The issue with your code The problem with the above approach is that if you forget releasing the connection after every single time you perform getDb you have a resource leak that might freeze your app eventually when it runs out of the resource you’re leaking. You might, in one place do: var users = … Read more
The .Net Garbage Collector calls the Object.Finalize method of an object on garbage collection. By default this does nothing and must be overidden if you want to free additional resources. Dispose is NOT automatically called and must be explicity called if resources are to be released, such as within a ‘using’ or ‘try finally’ block … Read more
Objects will be cleaned up when they are no longer being used and when the garbage collector sees fit. Sometimes, you may need to set an object to null in order to make it go out of scope (such as a static field whose value you no longer need), but overall there is usually no … Read more
Here are a couple of discussions explaining why Dispose is not necessary for a DataSet. To Dispose or Not to Dispose ?: The Dispose method in DataSet exists ONLY because of side effect of inheritance– in other words, it doesn’t actually do anything useful in the finalization. Should Dispose be called on DataTable and DataSet … Read more
You have to implement IDisposable interface methods: public void Dispose() { // Clear all unmanaged resources } Whenever you then instantiate your object you should do it inside a using statement using(Program3 p3 = new Program3()) { //do your job } // here the p3.Dispose gets called It is important to note that the point … Read more