fsprojects / fsprojects/Paket

Help in narrowing down issue with package not being added

Open
#4,022 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
F#
Stars
2.1k
Forks
528
Avg merge
1d 12m
Merged PRs (30d)
54

Description

Hi,

I've got a fairly big, complex solution (65 projects) the source of which I cannot share (work). In that solution I have a problem with a specific package not being added to a specific project, despite it appearing in paket.references etc. (While if I add a PackageReference to the project file, it works, so it's not a compatibility issue. There are also no error messages from paket.)

I tried to create a repro of this issue, but it turns out my original assumptions - that it has to do with the mix of net5 and netstandard2.0 projects and that specific package - was not correct.

Now I am a bit at a loss about how to proceed - is there any information/logs/whatever I can look at to try and narrow down the issue, other than performing a binary search of removing half the projects from the solution, check whether the problem is still there etc.?

Thanks,

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start from the reported Paket setup: a 65-project solution using paket.references, with net5 and netstandard2.0 projects and a package missing from one project. First gather the requested diagnostic information or logs and reduce the private solution to a minimal reproducible case; done means identifying why Paket omits the package or documenting the missing diagnostics needed to proceed.

Written by the indexing model from the issue text.

Assessment

Tech stack
fsharp
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.