How to port a .NET framework project to .NET Core including tests - A Guide
![Image](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhuFUSOg5uBM-pmvPnzzQsSolZxWn_FzJZrr5uBOo-BNA_jFtLwaNVTP_BcLT63coVuDtQcaxbfUCY03nJoN0IbRIpudEHPljib38d8LkgUXpC5AFLabZtpyXa1a10xPw1QSKaI_K9Zpi4/s640/API+Portability.png)
So you want to port your project to .Net Core and don't know how? Are you reluctant to let go of your traditional .Net Framework targeting but want to have a taste of the new .Net buzz? Is the information on the subject incomplete or too confusing (yes it usually is). Well you have come to the right place. TL;DR This is guide. It will hopefully save you time. Rejoice. A tale of two frameworks (well actually 3) I will make this one short and sweet and let this article tell the tale. I recommend to read this article before you continue: .NET Standard - Demystifying .NET Core and .NET Standard . To port or not to port It depends If this is your production code and there is no prospect to run it in a platform other than windows then maybe not. If it is a huge complicated project then maybe not If it is your open source baby maybe yes If it is a new project and you see the benefit of it being cross platform maybe yes The considerations are ...