Moved PackageOutputPath to NuGet's Pack targets

This should free the SDK from having to manage NuGet Pack's `PackageOutputPath` property. This was possible because of the `BaseOutputPath` that'll be used instead of `OutputPath` in the Pack targets.
dotnet · Mar 26, 2021 · 3838fec · 3838fec
1 parent 3978ab6
commit 3838fec
Showing 1 changed file with 1 addition and 6 deletions.
diff --git a/src/Tasks/Microsoft.NET.Build.Tasks/targets/Microsoft.NET.DefaultOutputPaths.targets b/src/Tasks/Microsoft.NET.Build.Tasks/targets/Microsoft.NET.DefaultOutputPaths.targets
@@ -40,10 +40,5 @@ Copyright (c) .NET Foundation. All rights reserved.
     <IntermediateOutputPath Condition=" $(IntermediateOutputPath) == '' and '$(PlatformName)' != 'AnyCPU' ">$(BaseIntermediateOutputPath)$(PlatformName)\$(Configuration)\</IntermediateOutputPath>
     <IntermediateOutputPath Condition="!HasTrailingSlash('$(IntermediateOutputPath)')">$(IntermediateOutputPath)\</IntermediateOutputPath>
   </PropertyGroup>
-
-  <!-- Set the package output path (for nuget pack target) now, before the TargetFramework is appended -->
-  <PropertyGroup>
-    <PackageOutputPath Condition="'$(PackageOutputPath)' == ''">$(OutputPath)</PackageOutputPath>
-  </PropertyGroup>
-
+
 </Project>