fsprojects / fsprojects/Paket

Update references leaves project files without any references

Open
#2,942 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description

Environment:

  • Visual Studio 2017 Professional, v15.3.3, v15.5.1, v15.5.2
  • Paket 0.38.3
    When I hit Visual Studio / Tools / Paket Dependencies Manager / Update all packages
    the update process starts and finishes seemingly without errors, and the paket.lock file correctly updated.
    But checking changes made to files shows that all the references are removed from .csproj files.
    There are multiple developers working on the same project, the issue affects us all.
Repro steps

(Don't know if it happens on any othe VS solutions, but in our case:)
Hit Visual Studio / Tools / Paket Dependencies Manager / Update all packages
the update process starts and finishes seemingly without errors, and the paket.lock file correctly updated.
But checking changes made to files shows that all the references are removed from .csproj files.

Expected behavior

References should be left intact.

Actual behavior

All refrences handled by paket are removed completely.

Known workarounds

After the update, using source control compare, restore the unwanted reference deletions.

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 with the Visual Studio Paket Dependencies Manager flow for “Update all packages” and compare the resulting paket.lock and .csproj changes. Reproduce the update and confirm that Paket updates paket.lock without removing Paket-managed project references from the .csproj files.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.