See dotnet/dotnet-docker#1147
Steps to reproduce
Start fxdependent powershell on win-arm or win-arm64
We have the following logic for deciding the SDK we want to use.
<Import Project="Sdk.props" Sdk="Microsoft.NET.Sdk" Condition="'$(RuntimeIdentifier)' ==
'win-arm' or '$(RuntimeIdentifier)' == 'win-arm64'" />
<Import Project="Sdk.targets" Sdk="Microsoft.NET.Sdk" Condition="'$(RuntimeIdentifier)' == 'win-arm' or '$(RuntimeIdentifier)' == 'win-arm64'" />
<Import Project="Sdk.props" Sdk="Microsoft.NET.Sdk.WindowsDesktop" Condition="'$(RuntimeIdentifier)' != 'win-arm' and '$(RuntimeIdentifier)' != 'win-arm64'" />
<Import Project="Sdk.targets" Sdk="Microsoft.NET.Sdk.WindowsDesktop" Condition="'$(RuntimeIdentifier)' != 'win-arm' and '$(RuntimeIdentifier)' != 'win-arm64'" />
When we build a framework dependent package, we have no specified RuntimeIdentifier, hence we select Microsoft.NET.Sdk.WindowsDesktop. We can only fix this in the next release for PowerShell.
Expected behavior
Actual behavior
Tries to load Microsoft.NET.Sdk.WindowsDesktop which is not supported.
Environment data
See dotnet/dotnet-docker#1147
Steps to reproduce
Start fxdependent powershell on win-arm or win-arm64
We have the following logic for deciding the SDK we want to use.
When we build a framework dependent package, we have no specified RuntimeIdentifier, hence we select
Microsoft.NET.Sdk.WindowsDesktop. We can only fix this in the next release for PowerShell.Expected behavior
Actual behavior
Environment data