Hi,
We have a UWP C++ project which consumes packages for 3 architectures (x86/x64/ARM) and 2 build configurations (Debug/Release).
Until recently (before .NET Core 3.0 and the associated Visual Studio 2019 16.3 release) the project restore its NuGet packages without any issue.
Since we upgraded to 16.3 and .NET Core 3.0 the following issue occurs on automatic restore:
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Microsoft.AppXPackage.Targets(5991,5): error APPX1101: packages\Microsoft.MixedReality.WebRTC.Native.Core.WinRT.x86.Release.0.2.1-preview-20190917.1\build\native\..\..\runtimes\win10-x86\native\Org.WebRtc.dll
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Microsoft.AppXPackage.Targets(5991,5): error APPX1101: packages\Microsoft.MixedReality.WebRTC.Native.Core.WinRT.x86.Debug.0.2.1-preview-20190917.1\build\native\..\..\runtimes\win10-x86\native\Org.WebRtc.dll
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Microsoft.AppXPackage.Targets(5991,5): error APPX1101: packages\Microsoft.MixedReality.WebRTC.Native.Core.WinRT.x64.Release.0.2.1-preview-20190917.1\build\native\..\..\runtimes\win10-x64\native\Org.WebRtc.dll
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Microsoft.AppXPackage.Targets(5991,5): error APPX1101: packages\Microsoft.MixedReality.WebRTC.Native.Core.WinRT.x64.Debug.0.2.1-preview-20190917.1\build\native\..\..\runtimes\win10-x64\native\Org.WebRtc.dll
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Microsoft.AppXPackage.Targets(5991,5): error APPX1101: packages\Microsoft.MixedReality.WebRTC.Native.Core.WinRT.ARM.Release.0.2.1-preview-20190917.1\build\native\..\..\runtimes\win10-arm\native\Debug\Org.WebRtc.dll
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Microsoft.AppXPackage.Targets(5991,5): error APPX1101: packages\Microsoft.MixedReality.WebRTC.Native.Core.WinRT.ARM.Debug.0.2.1-preview-20190917.1\build\native\..\..\runtimes\win10-arm\native\Debug\Org.WebRtc.dll
I tried various things like removing the Debug config and only using the Release packages, so that for each runtimes architecture there is a unique path, but that still fails. I also forces the path to use debug/release instead of $(Configuration), without success. Or added some Condition directive in the .props files, without success too. I can accept that NuGet doesn't support Debug+Release in the same package, but clearly not supporting win10-x86 alongside win10-x64 is unexpected.
.props files are publicly available on GitHub, see e.g. here. I know there are discrepancies with ARM (see the error above, which shows an extra Debug in the path) but even fixing those we still get an APPX1101 error.
Packages are available from nuget.org, e.g. here.
This is a blocker for releasing a v1.0 of our project, and several of our users already reported being affected.
Hi,
We have a UWP C++ project which consumes packages for 3 architectures (x86/x64/ARM) and 2 build configurations (Debug/Release).
Until recently (before .NET Core 3.0 and the associated Visual Studio 2019 16.3 release) the project restore its NuGet packages without any issue.
Since we upgraded to 16.3 and .NET Core 3.0 the following issue occurs on automatic restore:
I tried various things like removing the Debug config and only using the Release packages, so that for each
runtimesarchitecture there is a unique path, but that still fails. I also forces the path to usedebug/releaseinstead of$(Configuration), without success. Or added someConditiondirective in the.propsfiles, without success too. I can accept that NuGet doesn't support Debug+Release in the same package, but clearly not supportingwin10-x86alongsidewin10-x64is unexpected..propsfiles are publicly available on GitHub, see e.g. here. I know there are discrepancies with ARM (see the error above, which shows an extraDebugin the path) but even fixing those we still get an APPX1101 error.Packages are available from nuget.org, e.g. here.
This is a blocker for releasing a v1.0 of our project, and several of our users already reported being affected.