Skip to content

Conversation

@dsplaisted
Copy link
Member

Fix #32971

As part of the support for the artifacts output path format (#31454), I moved setting default values for Configuration, Platform, and PlatformName from Microsoft.NET.DefaultOutputPaths.targets to Microsoft.NET.Sdk.BeforeCommon.targets.

I missed that Microsoft.NET.DefaultOutputPaths.targets was also imported from Microsoft.NET.Sdk.BeforeCommonCrossTargeting.targets, so these properties were not defaulted correctly in the outer build anymore. This resulted in the OutputPath for the outer build having a doubled backslash in it, which impacted NuGet pack scenarios.

This copies the defaults for those properties to Microsoft.NET.Sdk.BeforeCommonCrossTargeting.targets, fixing the issue.

@dsplaisted
Copy link
Member Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Comment on lines +19 to +21
<Configuration Condition="'$(Configuration)'==''">Debug</Configuration>
<Platform Condition="'$(Platform)'==''">AnyCPU</Platform>
<PlatformName Condition="'$(PlatformName)' == ''">$(Platform)</PlatformName>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: ''=='' or '' == ''? Not sure what the standard is.

@marcpopMSFT marcpopMSFT merged commit 553a62f into dotnet:main Jun 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area-NetSDK untriaged Request triage from a team member

Projects

None yet

Development

Successfully merging this pull request may close these issues.

OutputPath contains double path separator leading to NU5019 in nuget pack

4 participants