3 ms·

Same here. I've tried moving my "boilerplate side project" .NET Framework template over to the latest and greatest about once a year over the past four years a

Same here. I've tried moving my "boilerplate side project" .NET Framework template over to the latest and greatest about once a year over the past four years and every time I hit the eight hour mark, I give up. Either my dependencies aren't supported yet, or there's some wonky versioning incompatibility, or there's some other undocumented frustration. I'm not dealing with anything wildly complex here ~ just an n-tier architecture supporting MVC rendered views, forms authentication, API endpoints, an EF middle-tier, and Azure SQL. About as simple as it gets for a web app. Has anyone here migrated from .NET framework > .NET core lately? Think it's time for me to give it another go?

zmj 7y ago
If your .NET Framework projects are in the old csproj style, first convert them to SDK style - no changes to the target runtimes or dependency versions. For asp.net, winforms, or wpf apps, this is usually the hard part. Once the app is working with SDK style projects, then try changing the runtime to netcoreapp. Often it just works; if it doesn't, you'll get useful error messages.