Paket Targetframework .NET >=4.6.2
Open
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Related: #2832
We continue to run into problems, when our packages use paths, that are too long.
As of .NET 4.6.2 this problem seems to be fixed: .NET Blog
Are there any plans to update the targetframework of paket to .NET >=4.6.2?
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 with related issue #2832 and the linked .NET 4.6.2 announcement. Inspect Paket's target-framework configuration and determine the compatibility impact of raising it to .NET 4.6.2; done means the target is updated without breaking supported environments and the long-path problem is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100