fsprojects / fsprojects/Paket

paket pack not functioning with net5.0 and mac

Open
#3,994 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description

It's not possible to use paket pack to package a nugget based on net5.0

Repro steps

using the following msbuild file

<?xml version="1.0" encoding="utf-8"?> <Project Sdk="Microsoft.NET.Sdk"> <PropertyGroup> <RootNamespace>Small</RootNamespace> <OutputType>Library</OutputType> <TargetFramework>net5.0</TargetFramework> </PropertyGroup> <ItemGroup> <Compile Include="Environment.fs" /> </ItemGroup> <Import Project="..\.paket\Paket.Restore.targets" /> </Project>

  1. run dotnet paket pack --version 1.2.0 .
Expected behavior

I would expect it to create the package/ a result similar to dotnet pack -c Release which succeeds

Actual behavior

The result is an error message Paket failed with -> Unable to find Release output path node in file <project_file_path>

Known workarounds

No known work arounds
Adding a specific OutputPath in the project file like <OutputPath>$(Configuration)/bin</OutputPath> removes the error message but the dll is not included in the nupkg (actually the entire lib folder Is missing)

dotnet version 5.0.100
OS: MacOS Big Sur 11.2.2
paket version 5.257

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

Reproduce the issue with the provided MSBuild project, the net5.0 target, macOS, and dotnet paket pack --version 1.2.0 .; compare it with dotnet pack -c Release. Trace how Paket locates the Release output path and builds the package. Done means the command succeeds and the nupkg contains the library DLL under its lib folder.

Written by the indexing model from the issue text.

Assessment

Tech stack
fsharp
Domain
build-system, release
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.