As is tradition, any new project (for a given definition of new) will be surpassed by the technology it uses. The project I’m currently working on was originally targeted to run on .NET Framework, and is doing a good job at it. However, being a new project we also have to be ready to run in the cloud, be scalable and, most importantly, future-proof. Since Microsoft has all but announced that .NET Framework will essentially be put in Maintenance Mode, .NET Core doesn’t seem like a bleeding-edge technology anymore, but the de facto standard of .NET right now.
The decision has been made: we are migrating our .NET Framework components and web apps to .NET Core! Exciting times, so first we need to assess what needs to be done to do this and document potential roadblocks and workarounds. Migrating is not a trivial task, so anything that can be done to make the transition smoother, is welcome.
This will (probably) be a series of posts about small(ish) things I found out and are good to know when you are migrating to .NET Core.