fsprojects / fsprojects/Paket

paket pack does not support AppendTargetFrameworkToOutputPath=false

Open
#3,971 2 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

Running paket pack on a project that has AppendTargetFrameworkToOutputPath set to false tries to look up the output assembly in ${OutputPath}\${TargetFramework} whereas the assembly is compiled into ${OutputPath}

Repro steps

Please provide the steps required to reproduce the problem

  1. Create a .NET Core class lib and set AppendTargetFrameworkToOutputPath to false.
  2. Create paket.template file
  3. Run paket pack
Expected behavior

Packing works.

Actual behavior
Loading /Users/agross/gw/grossweber/ops/source/Ops.Contracts/Ops.Contracts.csproj
Loading assembly metadata for /Users/agross/gw/grossweber/ops/build/bin/ops-host/bin/net5.0/Ops.Contracts.dll
Total time taken: 0 milliseconds
 - Runtime: 1 second
Paket failed with
-> DirectoryNotFoundException: Could not find a part of the path '/Users/agross/gw/grossweber/ops/build/bin/ops-host/bin/net5.0/Ops.Contracts.dll'.
   StackTrace:
   ...

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 a .NET Core class library whose AppendTargetFrameworkToOutputPath is false, a paket.template file, and paket pack. Start by tracing paket pack's output-assembly lookup; done means it finds the assembly directly under OutputPath and packing succeeds without the DirectoryNotFoundException.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.