I like very much the idea of a .NET Generic Host in the MSDN documentation:

An object that encapsulates an app’s resources, such as:

• Dependency injection (DI)
• Logging
• Configuration
• IHostedService implementations

At work, we are planning to migrate our WPF application from .NET Framework 4.7 to .NET Core 3.0. The main reason for doing so is that it was always a big pain to organize the updates of the .NET Framework on our customer machines. So being able to bundle .NET Core with our application is a big plus for us. Then, for sure, we are looking for the performance improvements brought by .NET Core and finally the new capabilities brought by the fast pace of innovation of .NET Core.

Let’ see in this blog post the new possibility offered by .NET Core 3.0 preview 2 to load and unload assemblies at run time using AssemblyLoadContext.

On Saturday, June 2, 2018, I had the chance to participate in the .NET Core Community online Hackathon.

As I got up really early this Saturday morning, I took the opportunity to participate. My goal was to see something new and learn a bit about how .NET Core is built and gain some new experience.

After running a first console app on my Raspberry Pi 3, I had to try ASP.NET Core and API. Two weeks ago when I posted “.NET Core console app running on Raspberry Pi”, I could make API working, but I had no chance with MVC. Today it worked!

Now that there is a distribution of .NET Core on a Linux distro running on my Raspberry Pi 3, I had to try it.

In this post, I will explain all the steps I had to execute to be able to run my first Hello World application.