fsprojects / fsprojects/Paket

Package restore can't mark package as dependency in Visual Studio

Open
#3,927 0 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

Description

When I add a package to the paket.references file and then restore the project, everything works fine except the packages folder (in the Solution Explorer) shows all the installed packages as a flat list.

When I install the same packages using NuGet it shows at the first level only the packages I installed and the package's dependencies are under those packages.

Any way to accomplish this behavior with Paket?

Repro steps
  1. Add log4net to the packet.dependencies with specified version (not sure if its related but that how I did it).
  2. Add the log4net to the paket.references
  3. Build the project.
Expected behavior

I really like to get the dependent behavior exists when installing NuGet package.

Actual behavior

Flat list.

Known workarounds

Live with the flat list.
The only issue is that I'm not sure what would happen when an innocent developer will by mistake open the Pakcages folder when it contains thousandths of packages...

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

Reproduce the restore using the paket.references file, the package dependency declaration, and log4net in Visual Studio. Start by observing how Paket populates the Packages folder in Solution Explorer; done means installed packages appear hierarchically, with direct packages containing their dependencies rather than a flat list.

Written by the indexing model from the issue text.

Assessment

Domain
developer-experience, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.