Skip to main content

WebActivator: How to control the order of execution?

One of the libraries we use during web development is WebActivator. WebActivator was introduced with NuGet to solve the following problem. 

With the current NuGet version it is not possible to alter existing code. This means that if you have a NuGet package that requires some extra coding executed (for example in the global.asax), that you need to add this extra code yourself, breaking the nice experience that NuGet gives you. To solve this issue, David Ebbo introduced WebActivator. This library allows you to add startup code in separate files instead of having to add it to your global.asax. This overcomes the current limitation of NuGet.

To use this library create an App_Start folder. Add a class file to this folder and include the following code:

using System;
[assembly: WebActivator.PreApplicationStartMethod(typeof(App_Start.MyApp), "PreStart")]
namespace App_Start 
{    
public static class MySuperPackage 
{
public static void PreStart() 
{            
// Add your start logic here
}    
}
}

And that's it! Now your code will be called early on when the app starts.

After adding a few of this Start classes, we hit a problem. Some of these start scripts had a dependency on each other, meaning that the order of execution did matter. It took us some time to discover the following feature:
Ability to run code after Application_Start

When you use a WebActivator PreApplicationStartMethod attribute, the method it points to runs before your global.asax’s.  There is an alternative attribute that runs after the very first HttpModule get initialized, called PostApplicationStartMethod!

[assembly: WebActivator.PostApplicationStartMethod(typeof(App_Start.MyStartupCode), "CallMeAfterAppStart")]

After changing some of the classes to the PostApplicationStartMethod,  everything worked.

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