• @happy_piwakawaka
    4•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
    • @[email protected]
      2•1 year ago

      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.

      • @happy_piwakawaka
        1•1 year 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).