Tiny Container Challenge: Building a 6kB Containerized HTTP Server

A funny post where we learn :

• the importance of docker multi-stage builds,
• the existance of an ultra miminal doker image called scratch ,
• that golang can produce pretty small binaries,
• that asm is really King.

Tiny Container Challenge: Building a 6kB Containerized HTTP Server!

How to prevent End of Life warning when building for deprecated .Net versions

With increasingly rapid evolutions of Framework, it is sometimes desirable to remain, for some projects, with deprecated versions of .Net.

It must be a conscious decision of the risks but you must be able to say “I accepted this risk and I don’t want to be bothered by these warnings anymore”.

One solution is to set precisely the version number of the SDK used for that compilation by using a global.json file. Doing so ensure you also use same deprecated SDK.

But you could prefer to use a more recent SDK while building for an ancient target.

And without warning. That’s exactly what CheckEolTargetFramework permit us to do: it’s a MSBuild property that can be set to to false to prevent warning NETSDK1138.

More on this subject on Fixing build warning NETSSDK1138 when building projects with end-of-life .NET frameworks.

Customizing Authorization Responses in .NET 5.0

Easy, we just have to implement an IAuthorizationMiddlewareResultHandler and regsiter it :

services.AddAuthorization(options => ...)

.AddSingleton<IAuthorizationMiddlewareResultHandler, MyAuthorizationMiddlewareResultHandler>();

More here: Customizing Authorization Responses in .NET 5.0 – Ben Foster.

REST and GraphQl compared

Interacting with APIs: REST and GraphQL | Google Cloud Blog

Short and concise: the minimum needed to introduce GraphQl to a non-developer audience that knows REST!