C#: should object variables be assigned to null?

by

No, and that could in fact be dangerous and bug-prone (consider the possibility that someone might try to use it later on, not realizing it had been set to null). Only set something to null if there’s a logical reason to set it to null.

More Related Contents:

  1. What is a NullReferenceException, and how do I fix it?
  2. Proper use of the IDisposable interface
  3. Do event handlers stop garbage collection from occurring?
  4. Unable to cast object of type ‘System.DBNull’ to type ‘System.String`
  5. Best Practice for Forcing Garbage Collection in C#
  6. Setting Objects to Null/Nothing after use in .NET
  7. Implementing IDisposable correctly
  8. Garbage collector and circular reference
  9. What is the difference between “x is null” and “x == null”?
  10. Dispose, when is it called?
  11. Checking if an object is null in C#
  12. Does garbage collection run during debug?
  13. .Net and Bitmap not automatically disposed by GC when there is no memory left
  14. Is it necessary to explicitly remove event handlers in C#
  15. Does garbage collector call Dispose()? [duplicate]
  16. GC.Collect()
  17. Monitoring Garbage Collector in C#
  18. Shortest way to check for null and assign another value if not
  19. How can I write a unit test to determine whether an object can be garbage collected?
  20. Why is there a difference in checking null against a value in VB.NET and C#?
  21. How to do ToString for a possibly null object?
  22. What is IDisposable for?
  23. Timer, event and garbage collection : am I missing something?
  24. String.IsNullOrWhiteSpace in LINQ Expression
  25. Nullable types: better way to check for null or zero in c#
  26. string.Empty vs null.Which one do you use?
  27. Does WeakReference make a good cache?
  28. How are String and Char types stored in memory in .NET?
  29. Force garbage collection of arrays, C#
  30. What is the operator precedence of C# null-coalescing (??) operator?

Leave a Comment