Open gfmatthews opened 1 year ago
Seems like the issue is that using AzDo task NuGetCommand@2
doesn't create the package as expected, which is what is used by the customer. Using DotNetCoreCLI@2
task works as expected and the package contains the files in the format expected. The suggestion here is to use that DotNetCoreCLI
instead. A working sample pipeline yml file was send to the user.
PR: Green-Software-Foundation/carbon-aware-sdk#279
1) Build the NuGet package using AzDo pipelines with built-in tools (i.e. AzDo's built-in dotnet pack and dotnet build)
Pull the built NuGet package into a new Visual Studio project.
EXPECTED: Package runs and no dependency issues are found
ACTUAL: Package fails when trying to find Azure Regions file