My biggest issue with .net core and .net in general, although .net core seems worse, is nuget issues and it causing issues with binding redirects.
Seems like every project I waste hours trying to figure out the mess that nuget creates.
Seems like every project I waste hours trying to figure out the mess that nuget creates.
They're usually caused by a mixup between local packages and the GAC, which .NET core doesn't use.
When you publish a .NET core application, you can publish as stand alone and see right there in the publish directory all the DLLs that are being used.
For example, because NuGet allows packages to import .props and .targets files you can have packages that add arbitrary references that don't match your target framework or runtime. Now you could say "oh, that's the package's fault, not NuGet's", but often the reason a package includes .props or .targets files is to work around other shortcomings in NuGet.
Has anyone here migrated from .NET framework > .NET core lately? Think it's time for me to give it another go?
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.