Doesn't dotnet paket pack use msbuild under the hood?
Open
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
For example, if I define package versions in the project as <Version>1.0.$(FooBar)</Version> and set FooBar environment variable to "2", dotnet pack produces package with version 1.0.2 whereas dotnet paket pack produces version 1.0.0.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the entry point for the dotnet paket pack command and trace how the project’s <Version> value is read compared with dotnet pack. Reproduce the case with FooBar set to 2; done means the Paket-generated package version matches the expected 1.0.2.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100