Manually destroy C# objects

by

You don’t manually destroy .Net objects. That’s what being a managed environment is all about.

In fact, if the object is actually reachable, meaning you have a reference you can use to tell the GC which object you want to destroy, collecting that object will be impossible. The GC will never collect any object that’s still reachable.

What you can do is call GC.Collect() to force a general collection. However, this almost never a good idea.

Instead, it’s probably better to simply pretend any object that doesn’t use unmanaged resources and is not reachable by any other object in your program is immediately destroyed. I know this doesn’t happen, but at this point the object is just a block of memory like any other; you can’t reclaim it and it will eventually be collected, so it may just as well be dead to you.

One final note about IDisposable. You should only use it for types that wrap unmanaged resources: things like sockets, database connections, gdi objects, etc, and the occasional event/delegate subscription.

More Related Contents:

  1. Do HttpClient and HttpClientHandler have to be disposed between requests?
  2. Using statement vs. IDisposable.Dispose()
  3. yield return statement inside a using() { } block Disposes before executing
  4. Questions about Entity Framework Context Lifetime
  5. Is it possible to force the use of “using” for disposable classes?
  6. Proper use of the IDisposable interface
  7. What are the uses of “using” in C#?
  8. What is the best workaround for the WCF client `using` block issue?
  9. Nested using statements in C#
  10. Why should you remove unnecessary C# using directives?
  11. When should I use “using” blocks in C#? [duplicate]
  12. How do I use the C#6 “Using static” feature?
  13. Async network operations never finish
  14. What happens if i return before the end of using statement? Will the dispose be called?
  15. Does foreach automatically call Dispose?
  16. Difference between destructor, dispose and finalize method
  17. Do I have to Close() a SQLConnection before it gets disposed?
  18. What is IDisposable for?
  19. Using the using statement in C# [duplicate]
  20. GC.Collect() not collecting immediately?
  21. When should I use GC.SuppressFinalize()?
  22. Who should call Dispose on IDisposable objects when passed into another object?
  23. What is the difference between using and await using? And how can I decide which one to use?
  24. Guidelines For Dispose() and Ninject
  25. using statement FileStream and / or StreamReader – Visual Studio 2012 Warnings
  26. Will a using block close a database connection?
  27. Do I need to Dispose a SemaphoreSlim?
  28. Who Disposes of an IDisposable public property?
  29. Determining if IDisposable should extend an interface or be implemented on a class implementing said interface
  30. Using various types in a ‘using’ statement (C#)

Leave a Comment