When should I use Lazy?

by

You typically use it when you want to instantiate something the first time its actually used. This delays the cost of creating it till if/when it’s needed instead of always incurring the cost.

Usually this is preferable when the object may or may not be used and the cost of constructing it is non-trivial.

More Related Contents:

  1. caching the result from a [n async] factory method iff it doesn’t throw
  2. How to get ToolTip from WPF Data Grid Column Header (DataGridTemplateColumn) in code?
  3. How do you simulate Mouse Click in C#?
  4. Checking for directory and file write permissions in .NET
  5. How can I get a list of users from active directory?
  6. Build query string for System.Net.HttpClient get
  7. Collection versus List what should you use on your interfaces?
  8. How to fix a opacity bug with DrawToBitmap on WebBrowser Control?
  9. How to unload an assembly from the primary AppDomain?
  10. Checking file/folder access permission
  11. “Requested URI is invalid” during upload with FtpWebRequest
  12. Executing query with parameters
  13. Parse C# string to DateTime
  14. ConfigureAwait pushes the continuation to a pool thread
  15. Flip the GraphicsPath that draws the text/string
  16. iTextSharp Creating a Footer Page # of #
  17. Regex replace multiple groups
  18. C#/.NET analysis tool to find race conditions/deadlocks
  19. Caching in C#/.Net
  20. Is DataContract attributes required for WCF
  21. What does Process.Dispose() actually do?
  22. Join and Include in Entity Framework
  23. Error in Process.Start() — The system cannot find the file specified
  24. Difference between .Net Core, Portable, Standard, Compact, UWP, and PCL?
  25. String.Format exception when format string contains “{“
  26. C# tutorial to write gadgets
  27. How to implement Security Protocols TLS 1.2 in .Net 3.5 framework
  28. Implementing a timeout on a function returning a value
  29. Fire Form KeyPress event
  30. How to modify my App.exe.config keys at runtime?

Leave a Comment