Azure-pipelines-tasks: Nuget pack command cannot find build output for multiple targets

[alexwiese]

Using the default .NET Core (.NET Framework) template on VSTS.
The build is output to the following locations (for both framework targets specified in the csproj):

\bin\release\net461\output.dll
\bin\release\netstandard1.6\output.dll

The Nuget task (version 2.0.5) looks for the output in the wrong location:

NuGet.CommandLine.CommandLineException: Unable to find 'bin\release\output\bin\release\'. Make sure the project has been built.

[alexdrl]

This is related to https://github.com/NuGet/Home/issues/5832 and not related to the build task. We made a workaround using GeneratePackageOnBuild for .NET Standard libraries.

[keithrob]

Closing this out based on previous comment.

[verndemille]

This fails on a .NET framework pack that references a .NET Standard core library.

[chris-strauss]

Has this been resolved? In Azure Dev Ops when adding a nuget task to pack a multi-targeted project it is appending a bin/release path to the beginning of the directory structure.

2019-02-01T18:34:47.7556973Z ##[error]The nuget command failed with exit code(1) and error(Unable to find 'bin\release\solutionfolder\bin\release

[Sreini]

@chris-strauss we are having the exact same issue still. Any progress on this? Did you find a workaround?

[Dejulia489]

I assume this is still an issue. Has anyone found a work around?

[chris-strauss]

@chris-strauss we are having the exact same issue still. Any progress on this? Did you find a workaround?

@Sreini I had removed the Pack task from the pipeline and had the project pack on build.