The big news in the evolution of Microsoft .Net is the move towards a unified .Net platform that can support development for every kind of device and every kind of application. At the moment the .Net ecosystem is still somewhat fragmented – we have:
.Net 5 (due for release in 2020) will be the first unified version of .Net.
Here at IJYI, .Net Framework was originally our main development platform, so we have been following these changes with a great deal of interest. We are incrementally adopting the new versions of .Net Core as they come along, which means that we no longer create .Net Framework projects, and where feasible we have migrated existing framework projects to use .Net Core.
There are many interesting articles out there that give great high-level comparisons of .Net Framework and .Net Core:
https://www.c-sharpcorner.com/article/difference-between-net-framework-and-net-core/https://stackify.com/net-core-vs-net-framework/
https://mitchelsellers.com/blogs/2018/07/19/should-when-and-how-can-i-migrate-to-net-core
In this post I am going to focus on the IJYI experience of moving to .Net Core and talk about some of our observations so far:
At the time of writing we are eagerly awaiting .Net Core 3 and the performance improvements it promises. In a future post I will consider:
About the author
IJYI Ltd
IJYI Ltd.