this post was submitted on 21 Jun 2023
9 points (100.0% liked)

.NET

1484 readers
5 users here now

Getting started

Useful resources

IDEs and code editors

Tools

Rules

Related communities

Wikipedia pages

founded 1 year ago
MODERATORS
 

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
[–] happy_piwakawaka@lemmy.nz 1 points 1 year ago

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