Paket icon indicating copy to clipboard operation
Paket copied to clipboard

paket pack does not support AppendTargetFrameworkToOutputPath=false

Open agross opened this issue 5 years ago • 2 comments

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:
   ...

agross avatar Dec 19 '20 10:12 agross

The latest alpha release can handle AppendTargetFrameworkToOutputPath correctly. You could give it a try.

lithriandel avatar Aug 31 '22 06:08 lithriandel

The latest alpha release can handle AppendTargetFrameworkToOutputPath correctly. You could give it a try.

Seems to work fine!

agross avatar Sep 09 '22 19:09 agross