Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Users Search
Help Dashboard Sign In Sign Up
Q&A Code Reviews Meta
Q&A
Posts Tags Edits
Ask Question

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?

+2
−0

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:

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.

.net-core nuget paket
posted 8 months ago
CC0
8mo ago
user card
toraritte‭
640 reputation 32 16 99 53
History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

Self-answered? (4 comments)
Self-answered?
Karl Knechtel‭ wrote 8 months ago
copy link

Even if you are not confident in your findings below the line, they certainly come across as a sincere attempt to answer the question above the line. It should be posted as an answer instead. This is a perfectly acceptable and encouraged use of the site software.

toraritte‭ wrote 8 months ago
copy link

Thank you for the encouragement! I thought about that, because those points do sound plausible, but I have just started out with .NET in earnest, so it is just guesswork. I also didn't want to discourage answers.

If no-one refutes those points in a day or two, I'll definitely post them as answers instead.

Michael‭ wrote 8 months ago
copy link

I'll definitely post them as answers instead.

Please do! Even if others answer the question later, it makes it easier for them to refer to your answer in a link if it already exists, rather than quoting text from the question that you may move to an answer later.

toraritte‭ wrote 8 months ago
copy link

Thank you again! I just moved my comments into an answer, and also quoted an answer from Stackoverflow that confirms my assumptions. Have a great day!