fsprojects / fsprojects/Paket

paket install and paket auto-restore on use different places in project file to insert paket.targets

Open
#2,045 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement msbuild proj sdk: verbose sdk up-for-grabs
Dominant language
F#
Stars
2.1k
Forks
528
Avg merge
1d 12m
Merged PRs (30d)
54

Description

Description

Paket version 3.30.0

Commands paket auto-restore on and paket install put <Import Project="..\..\.paket\paket.targets" /> into different places of the project file, it causes unnecessary changes. It occurs for example in the case we add new project to solution.

Repro steps

Get the new project with paket as dependency manager.

  1. Run paket auto-restore on
  2. Commit the changes
  3. Run paket install
Expected behavior

No changes in the repository

Actual behavior

Several project files are changed, and the change is simple - place of include of paket.targets

image

Known workarounds

Always run paket install after paket auto-restore on

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 by reproducing the reported sequence with paket auto-restore on and paket install, then compare the project files after each command. Trace the project-file insertion paths for both commands; done means both place the paket.targets import consistently and running the second command produces no unrelated project-file changes.

Written by the indexing model from the issue text.

Assessment

Tech stack
fsharp
Domain
build-system, 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.