Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Comments on .NET dependency management: `dotnet add package` vs. Paket?
Post
.NET dependency management: `dotnet add package` vs. Paket?
Many older projects (i.e., older than 5 years) provide instructions to the Paket .NET dependency manager (e.g., Suave), so I started digging into it, got confused, then gave up for while because errors kept cropping up and I just wanted to make progress.
I reached a point in my project where I have to add packages properly (instead of just pulling them in on the CLI when testing), so I did a search for the term dotnet add external package project to solution where the most prominent results were:
-
[Microsoft Learn] Install and manage NuGet packages with the
dotnetCLI -
[Microsoft Learn]
dotnet add packagecommand - .NET CLI
After reading, dotnet add package looks exactly what Paket is doing: adding NuGet packages to a .NET project. Am I missing something?
edit: Suave's NuGet page seems to confirm that they provide the same functionality, but, unlike the .NET CLI instructions, there is a warning below the Paket ones, implying that it is a third-party solution:
The NuGet Team does not provide support for this client. Please contact its maintainers for support.
1 comment thread