Skip to main content

Instantiating types with no public constructors

In some occasions you want to instantiate a type without a public constructor. Why should you want to do this?

For example, imagine you have a customer class in your system. One of the rules you always try to follow is that an object can never be in an invalid state. For the customer class this means that we always need at least a firstname and lastname. How can we make sure that a customer always has these two values? That's easy.

By using a public constructor that asks you to provide these two values and by readonly properties for first and lastname, you're certain that your customer object is valid.

But when your data layer is fetching customers from the database, it's far more easy to let it use a parameterless constructor than when it has to call your constructor with two parameters(in the assumption that you want to make your data layer as generic as possible). So in that case you can add a second protected constructor without any parameters. No one from outside the class can call this constructor, so developers will always use the constructor with the first and lastname parameter.

Anyway, how can you get this done? One of the overloads of the Activator.CreateInstance method makes this possible.

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...

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.

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...