Blog

Add Swagger & API Explorer to .Net Core App 3.1

Nugets Microsoft.AspNetCore.Mvc.NewtonsoftJson Microsoft.AspNetCore.Mvc.Versioning.ApiExplorer Microsoft.Data.SqlClient Microsoft.Extensions.Http Newtonsoft.Json Swashbuckle.AspNetCore Setting up Swagger and API Explorer using Microsoft.AspNetCore.Buil…

Port .NET Console App to .Net Core App 3.1

Project Keep current project in tact. This is similar in practice as applying the strangler pattern. Doing so will keep the project as a point of reference. More importantly, it keeps the compiler happy and allows for porting each project independently. W…

Port .NET UnitTest to .Net Core App 3.1

Project Keep current project in tact. This is similar in practice as applying the strangler pattern. Doing so will keep the project as a point of reference. More importantly, it keeps the compiler happy and allows for porting each project independently. W…

Port .NET WebApp to .Net Core App 3.1

Microsoft .NET Framework was first released on February 12, 2002 and has since been a very active set of languages and framework. Although it is very hard to determine the number of project across the globe, we can guesstimate the number, what is considered legacy apps, to be in the 10s of thousands. By legacy, I mean projects written pre .NET Core - a modern compiler and framework redesigned to run on cloud native environment. Moving from legacy to modern compiler and framework does not have to mean porting your app to a new language and rewriting decaded of business logic. 😉