Welcome back! If you missed Part 1, you can check it out here.
The .NET framework is undoubtedly a powerful tool with which to build applications. Incorporating it on serverless platforms unlocks myriad architectural and cost-related benefits. However, the serverless ambitions of .NET developers are often dashed by unendurable cold start durations. This is mainly attributed to how .NET assemblies are jitted which, among other issues, puts a lot of stress on serverless containers starting up. Nevertheless, there are solutions to the overbearing problem, and that is the purpose of this piece: to highlight the solutions any .NET developer can implement to drastically reduce cold start durations and, ideally, even eliminate them completely.