Creating Common Intermediate Language projects with .NET SDK

When you compile your C#, F# or VB.NET code, which are all high-level managed languages, the relevant compiler doesn’t compile it to native code, but instead it compiles it into the Common Intermedia Language.

The IL code is then just-in-time (not always, but let’s keep things simple) compiled by the CLR/CoreCLR to machine code that can be run on the CPU. What I wanted to show you today, is that with the new Microsoft.NET.Sdk.IL project SDK, it is actually quite easy to create and build projects in pure IL.

Let’s have a look.

Project SDKs

The new project system for .NET allows usage of custom project SDKs to support building a wide array of application types. You add an SDK to your project at the top of the project file, for example, the standard one for libraries and console apps is Microsoft.NET.Sdk.

There are quite a few other project SDKs – ASP.NET Core uses Microsoft.NET.Sdk.Web, .NET Core workers use Microsoft.NET.Sdk.Worker and so on. For the most part these things do not really concern the developers, as they are set from the project template and then never change.

One interesting project SDK that is not widely known, is Microsoft.NET.Sdk.IL. It allows us to write .NET code (libraries, applications) using pure IL, instead of a higher level language. This can then be built via dotnet CLI, using ILASM as desktop FX, .NET Core or .NET Standard.

Getting started with Microsoft.NET.Sdk.IL

The SDK is actually not published to the public NuGet feed – therefore to take advantage of it, you need to add a custom NuGet feed of Core CLR to your NuGet.config.

This is the old feed, but it’s where we can find the “old” version of the SDK, that was built for .NET Core 3.0. On the new feed, there is currently only latest build available, that’s already adapted towards .NET 5.0 (or .NET Core 5.0, the name is apparently not set yet).

Once the feed is added, you could also add the following global.json file, indicating that the SDK of this particular version should be used:

Bootstrapping an IL project

Equipped with such setup, we could create our project. The extension for IL projects is ilproj, but structurally it is very similar to csproj.

In my case it will look the following:

We are specifying here the reference to the Microsoft.NET.Sdk.IL SDK again, as well as the version of the ILASM package, which should be the same as the SDK itself.

I will be building for .NET Standard 2.0 only, but there is nothing preventing you from targeting other frameworks. For each of the supported frameworks, you could create an include folder in order to include certain common references. In my case, I will include the reference to the CorLib. To do that I create the path include\netstandard\coreassembly.h with the following contents:

Writing IL code

At this point, the only thing left is to write some IL code. I therefore create a and, first, need to import the inclusion of core lib, as well as define the assembly and module. This is the bare minimum that is needed.

The rest will be my regular code – since this is a library not a console app, I do not need to create an entry point. I will, however, create a Hello type, with a World() method (sounds particularly exciting, doesn’t it?).

With this code in place, we can now build our program using a regular dotnet build {path-to-my.ilproj} command. The output should look more or less like this:

At that point we have a valid DLL we can load from any project compatible with .NET Standard 2.0 and use it. In this case, at the C# surface level, the usage would simply be:

What can you do with this?

Well, obviously, you can let your imagination be the limit. The most apparent use case is to do all kinds of micro-optimizations, especially if you feel like the compiler is not doing enough. That said, you could also do some completely absurd things with it too – after all it’s raw IL.

For example, you could remove the inheritance from System.Object:

and add an ILASM switch to disable automatic inheritance to our ilproj:

This DLL will now build correctly, and we have managed to achieve the impossible – we now have a DLL, that was successfully emitted, where we have a type that doesn’t inherit from System.Object, which is really forbidden. As thrilling as this is, it is, unfortunately, equally useless, since any attempt to load and use this DLL will result in a type load exception.

We could also, given the fact that we are in IL, do some other things that are forbidden in C#. For example overload by return type. I could add a second World() method to our Hello type – differing from our previous one by return type only:

We now have two Hello.World() methods, one returning a string and one returning an int. This is impossible to do in C# and the compiler would not allow it, but it’s allowed in IL, since you have to specify the return type when you call a method there.

So this DLL builds, and a quick peek via decompiler reveals that indeed our plot worked and we have a DLL that really is impossible to produce with C# code and the Roslyn compiler:

To be fair, again, when we try to use it from a C# program, and invoke Hello.World() there, the compiler will not know which method to select and complain:

What is interesting is that it would work with reflection, for example, the following code compiles and executes just fine:


These are all little useless hacks and quirks, but hopefully they illustrate the really cool aspect of being able to just write raw IL. The code from this article is available on Github. I hope it will help you get started building IL projects.

For “real world” use cases I recommend you check out System.Runtime.CompilerServices.Unsafe which is build using the Microsoft.NET.Sdk.IL SDK. The library can be used to do a bunch of unsafe operations like unsafe casts – in a way that would not be possible to be expressed in C#.