Skip to main content

.NET 4.0 becomes lazy...

If you just think, you have discovered all the exciting new features in .NET 4.0, you always find some new bits of nice functionality.

Lazy<T> is one of those features.

It brings lazy loading to the core of the .NET framework. Suppose that you have an object that is very expensive to create and use. You don’t want to create it everytime your application runs. You only want to create it when you need it. Lazy<T> makes this easy.  You just create a lazy wrapper on the expensive object: 

   1:  Lazy<ExpensiveResource> ownedResource = new Lazy<ExpensiveResource>();

To get the expensive object just use the ownedResource.Value property. The first time you access ownedResource.Value, the expensive resource will get allocated, but not before.

And the API designers did a really good job and added two very useful constructions:

First, Lazy<T> has an overloaded constructor that allows you to specify a Func<T>. This makes it possible to use a factory method to construct your object. No new() constraint that limits the usability of this class. 

   1:  public Lazy(Func<T> valueFactory)

Second, there are two other constructors in Lazy<T>: 

   1:  public Lazy(LazyExecutionMode mode); 
   2:  public Lazy(Func<T> valueFactory, LazyExecutionMode mode);


These two constructors indicate that you are running in a multi-threaded environment, and the lazy construction of the owned object must be synchronized. So you are assured that only one thread will actually create the object.

It makes me wonder what other things are out there in the .NET 4.0 Framework...

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more