fsprojects / fsprojects/Paket

comparison with nuget client to help new users evaluate differences

Open
#2,736 12 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

documentation enhancement UX
Dominant language
F#
Stars
2.1k
Forks
528
Avg merge
1d 12m
Merged PRs (30d)
54

Description

I'm evaluating whether to stay with Nuget (using 3.5, I've been turned off by the amount of unsupported features that used to work in v2) or switch to Paket and I'm having hard time finding information about packaging entire solutions or whole MVC projects (or single areas, with their Views, scripts, images, etc.) with Paket.

I have a working solution using NuGet 2 but obviously have to make a step forward. NuGet developers do plan to bring the content packaging back (not the content transforms though, which I also use) so I'd like to know about the content packaging roadmap with Paket.

Also, I cannot seem to find any docs on it, is there a convention about the folder structure to follow or something similar to what NuGet (v2) had?

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 reviewing Paket’s current documentation and comparing it with the NuGet 2 behavior described in the issue. Establish whether complete solutions or MVC projects, content packaging, content transforms, and folder conventions are supported, then document the confirmed behavior and any roadmap information.】【。

Written by the indexing model from the issue text.

Assessment

Domain
documentation, tooling
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.