The .net garbage collector will eventually free up memory, but what if you want that memory back immediately? What code do you need to use in a class myclass to call myclass.dispose and free up all the used space by variables and objects in myclass? ...
Hi, I have a "Status" class in C#, used like this: Status MyFunction() { if(...) // something bad return new Status(false, "Something went wrong") else return new Status(true, "OK"); } You get the idea. All callers of MyFunction should check the returned Status: Status myStatus = MyFunction(); if ( ! myStatus.IsOK() ...
The .NET IDisposable Pattern implies that if you write a finalizer, and implement IDisposable, that your finalizer needs to explicitly call Dispose. This is logical, and is what I've always done in the rare situations where a finalizer is warranted. However, what happens if I just do this: class Foo : IDisposable { public void Dis...
I've got a C# class with a Dispose function via IDisposable. Its intended to be used inside a using block so the expensive resource it handles can be released right away. Problem is that a bug occurred when an exception was thrown before Dispose was called, and the programmer neglected to use using or finally. <rant> In C++, I never ha...
Can I use this approach efficiently? using(SqlCommand cmd = new SqlCommand("GetSomething", new SqlConnection(Config.ConnectionString)) { cmd.Connection.Open(); // set up parameters and CommandType to StoredProcedure etc. etc. cmd.ExecuteNonQuery(); } My concern is : Will the Dispose method of the SqlCommand (which is calle...
In Visual Studio, when I type the line "Implements IDisposable", the IDE automatically adds: a disposedValue member variable a Sub Dispose() Implements IDisposable.Dispose a Sub Dispose(ByVal disposing As Boolean) The Dispose() should be left alone, and the clean up code should be put in Dispose(disposing). However the Dispose Final...
The ThreadStatic attribute declares a static variable as unique-per-thread. Do you know an easy pattern to correctly dispose such variables? What we used before ThreadStatic is a ThreadContextManager. Every thread was allocated a ThreadContext which retained all thread-specific information. We spawned some threads and let them work. The...
I've got a class named BackgroundWorker that has a thread constantly running. To turn this thread off, an instance variable named "stop" to needs to be "true". To make sure the thread is freed when the class is done being used, I've added IDisposable and a finalizer that invokes Dispose(). Assuming that "stop = true" does indeed cause ...
I have a class which implements UserControl. In .NET 2005, a Dispose method is automatically created in the MyClass.Designer.cs partial class file that looks like this: protected override void Dispose(bool disposing) { if (disposing && (components != null)) { components.Dispose(); } base.Dispose(disposing...
Is there a method, or some other light-weight way, to check if a reference is to a disposed object? P.S. - This is just a curiousity (sleep well, not in production code). Yes, I know I can catch the ObjectDisposedException upon trying to access a member of the object. ...
Hi, I have an abstract base class with a TcpClient field: public abstract class ControllerBase { internal protected TcpClient tcpClient; It has a method to setup a connection: private void setupConnection(IPAddress EthernetAddress, ushort TcpPort) { if (this.tcpClient == null || !this.tcpClient.Connected) { ...
I have a singleton that uses the "static readonly T Instance = new T();" pattern. However, I ran into a case where T is disposable, and actually needs to be disposed for unit tests. How can I modify this pattern to support a disposable singleton? The interface I would like is something like: var x = Foo.Instance; var y = Foo.Instance; ...
Does anyone have a good articles or tutorial on correctly using dispose and IDisposable. I am trying to explain this to some junior dev and wanted to get some extra material, examples, etc. ...
For general code, do I really need to dispose an object? Can I just ignore it for the most part or is it a good idea to always dispose an object when your 100% sure you don't need it anymroe? ...
I am cleaning up the DataReaders in an old .NET 1.1 project that I inherited. The previous developer coded the data-access-layer in such a way that most of the DAL methods returned SqlDataReaders (thus leaving it up to the caller to properly call the .Close() or .Dispose() methods). I have come across a situation, though, where a cal...
Is there a catch or hidden problem in using a DisposableBase base class instead of recoding the Dispose pattern on every class? Why aren't everyone using such a relevant class? Edits: I naturally only meant classes that implement IDisposable I know it uses up the option for inheritance, but I'm willing to pay the price (at least when...
Vista SP1 Visual Studio 2008 SP1 .NET 3.5 SP1 C# I have a winforms app I'm playing with that uses a SerialPort object as a private variable. When the application is compiled and executed, it works great. It also works running in debug mode wihtout any breakpoints. 90% of the time when I stop at a breakpoint and try to step through code ...
Hi, I'd like to know when i should and shouldn't be wrapping things in a USING block. From what I understand, the compiler translates it into a try/finally, where the finally calls Dispose() on the object. I always use a USING around database connections and file access, but its more out of habit rather than a 100% understanding. I kn...
Hi folks, I'm making a simple Image Debugger Visualizer. Code is below. I'm not sure if i need to manually dispose of the Image instance? Because i'm making a windows Form window and the PictureBox inside that contains my dynamic image .. do i need to add some special code when the form is terminating, to dispose of this? here's the...
Simple case: i put a DataTable in Cache DataTable table = SomeClass.GetTable(); Cache["test"] = table; then in later calls i use DataTable table = (DataTable)Cache["test"]; now the question is: should i call table.dispose() on each call, though its stored in the Cache? Means the object is always the same? Or will Cache create a copy...