3 ms·

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 e

by LandR 7y ago

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.

marsrover 7y ago
I really don't understand how you're having binding redirect issues with .NET core. 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.
- lazulicurio 7y ago
  There's still plenty of ways reference resolution with NuGet can go wrong, even without the GAC. 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.
moron4hire 7y ago
.NET Standard 2 relaxed the versioning requirements that led to so many binding redirects.
autechr3 7y ago
.net core is definitely better than .net framework in regards to nuget issues in my experience.
fstopmick 7y ago
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.

by LandR 7y ago

marsrover 7y ago

I really don't understand how you're having binding redirect issues with .NET core. 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.

lazulicurio 7y ago
There's still plenty of ways reference resolution with NuGet can go wrong, even without the GAC. 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.

moron4hire 7y ago

.NET Standard 2 relaxed the versioning requirements that led to so many binding redirects.

autechr3 7y ago

.net core is definitely better than .net framework in regards to nuget issues in my experience.

fstopmick 7y ago

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.