this post was submitted on 21 Jun 2023
28 points (93.8% liked)

.NET

1503 readers
3 users here now

Getting started

Useful resources

IDEs and code editors

Tools

Rules

Related communities

Wikipedia pages

founded 2 years ago
MODERATORS
erlingur
starman
Spyros
28
What do you find most frustrating about .NET? (programming.dev)
submitted 2 years ago* (last edited 2 years ago) by sisyphean to c/dotnet
35 comments fedilink hide all child comments
 

The original thread is on the devil’s website and I don’t want to direct traffic to it, so here’s a link to the tweet instead:

https://twitter.com/davidfowl/status/1671351948640129024?s=46&t=OEG0fcSTxko2ppiL47BW1Q

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 4 points 2 years ago (1 children)

NuGet. The whole package management experience just feels so disjointed and tacked sometimes.

  • VS package management is (search, upgrade) slow and buggy
  • Central Package Management works for the CLI but is not implemented properly in VS, and is not available for Framework projects
  • The Azure credential manager, for Azure based NuGet feeds, is hard to configure reliably
  • Don't even start me on issues querying / publishing NuGet packages via PowerShell
[–] nibblebit 2 points 2 years ago (1 children)

I agree that credential management can be tricky. But genuinely after working from framework to core for over 15 years, publishing an consuming packages has been the best experience for me out of all other ecosystems. Maybe node is easier, but I've been burned too many times by supplychain issues to feel safe with it.

There was a period between 2016-2019 where due to error codes and no error messages it was a bit trickier to resolve the 'yellow triangle of doom'.

But honestly compared to pip and cargo and Gradle Nuget has been a damn godsend.

[–] [email protected] 1 points 2 years ago

Yeah I agree. Minor frustrations in the grand scheme of things, it's my top frustration only because I really don't have any other frustrations with the ecosystem.

I'd take NuGet over Npm any day, and it's far far better than the old days of dll hell (I still curse Log4Net).