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 »
Q&A

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 How to automatically add package reference into project file after installing .NET package?

Parent

How to automatically add package reference into project file after installing .NET package?

+2
−0

Just getting into F#, finally figured out how to add .NET packages to projects, but the way I managed to get it to work doesn't make sense. Once the package is installed (either with nuget or paket), I have to manually add a reference to the project file (either by editing it directly or with dotnet add package). This extra step is usually automated with other languages, so I presume that I'm doing something wrong.

These are the steps I did on a Mac M1:

  1. "Install" F#

    nix-shell -p dotnet-sdk_7
    
  2. Follow all the steps in Get started with F# with command-line tools - .NET | Microsoft Learn. (No errors.)

  3. Install paket following the install guide.

  4. Follow the walkthrough on adding dependencies.

    Specifically:

    1. added nuget FSharpPlus to paket.dependencies
    2. created the src/App/paket.references with the the line FSharpPlus
    3. ran dotnet paket install

    Once done, simply added open FSharpPlus to src/App/Program.fs, and ran dotnet restore followed by dotnet build, which blew up with

    error FS0039: The namespace or module 'FSharpPlus' is not defined.
    

The fix was simple enough,

dotnet add src/App/App.fsproj package "FSharpPlus" --version "1.5.0"

but it's hard for me to believe that one has to add these references manually for each package.


update: Alright, I'm officially clueless. Just out of curiosity, I added open Giraffe.Htmx to src/App/Program.fs, then ran

dotnet add src/App/App.fsproj package "Giraffe.Htmx" --version "1.9.6"
dotnet build

and everything worked... So what is the point of using paket or nuget then?

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

Post
+1
−0

Once the package is installed (either with nuget or paket), I have to manually add a reference to the project file (either by editing it directly or with dotnet add package).

You don't have to do that. Paket isn't really user-friendly so you may think you have to add reference to a package twice.

Paket is a dependency manager for .net projects but it's not the most used one.

Using just dotnet cli (or edit .fsproj manually) is more than enough for most cases. So best to avoid Paket until you get some confidence in dotnet world.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

1 comment thread

`paket` may be overkill, but why is it not working? (3 comments)
`paket` may be overkill, but why is it not working?
toraritte‭ wrote 4 months ago

Thank you for the answer! I did some digging in the meantime, and indeed the consensus is that using paket pays off mostly when the project reaches a certain level of complexity.

So I'm not going to worry about it as my project is not a big one. What gnaws at me is that I can't figure out why it is not working (i.e., why the paket commands also update the .fsproj file, so that dotnet build would go through). Anyway, maybe I'm doing something wrong, so I'll just give it another shot a bit later.

FoggyFinder‭ wrote 4 months ago

I didn't use paket for quite a while. Don't remember I ever used it with modern dotnet so not sure. I'll try to check it on weekends. No promise though.

toraritte‭ wrote 4 months ago

Thanks, but please don't bother - I just realized that the books I've been reading were written before .NET Core, when it probably made more sense to use it...