Paket for new .NET generated apps
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
First of all, i'm new to the .NET world, sorry if my questions are stupid.
Everytime I generate a new .NET app on my Linux from scratch using $ dotnet new <TemplateName> it generates automatically NuGet files in the obj directory. My questions are :
- Are these files redundant with Paket and can cause problems together ?
- Can these files be deleted if I want to use Paket and its .lock and .dependencies files?
- Is there a way to indicate .NET to use Paket by default to generate the new app with Paket, or something like this ?
Thank you very much for your time.
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 the dotnet new <TemplateName> entry point and inspect the generated NuGet files in obj alongside Paket's .lock and .dependencies files. Determine whether they overlap, whether the generated files can be removed, and whether default Paket generation is supported; document the findings and any required configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100