You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug report (I searched for similar issues and did not find one)
Current behavior
Currently Windows SDK 17704 is installed during the build process, however, certain managed applications and DLLs will fail on non-Insiders OS because of the way they are signed. Most notably this includes Microsoft.Windows.UI.Xaml.Build.Tasks.dll, which is required for UWP applications. Should a UWP application target 17704, the application would fail to compile.
Expected behavior
UWP applications targeting 17704 should compile during CI as expected.
Minimal reproduction of the problem with instructions
Environment
Nuget Package(s):
Package Version(s):
Windows 10 Build Number:
- [ ] Creators Update (15063)
- [ ] Fall Creators Update (16299)
- [ ] April 2018 Update (17134)
- [ ] Insider Build (build number: )
App min and target version:
- [ ] Creators Update (15063)
- [ ] Fall Creators Update (16299)
- [ ] April 2018 Update (17134)
- [ ] Insider Build (xxxxx)
Device form factor:
- [ ] Desktop
- [ ] Mobile
- [ ] Xbox
- [ ] Surface Hub
- [ ] IoT
Visual Studio
- [ ] 2017 (version: )
- [ ] 2017 Preview (version: )
A solution discussed by @onovotny and I is to disable strong name checking in the registry as part of the SDK installation to ensure test/delay signed applications and DLLs will execute during the build
I'm submitting a...
Current behavior
Currently Windows SDK 17704 is installed during the build process, however, certain managed applications and DLLs will fail on non-Insiders OS because of the way they are signed. Most notably this includes
Microsoft.Windows.UI.Xaml.Build.Tasks.dll
, which is required for UWP applications. Should a UWP application target 17704, the application would fail to compile.Expected behavior
UWP applications targeting 17704 should compile during CI as expected.
Minimal reproduction of the problem with instructions
Environment
CC: @onovotny
The text was updated successfully, but these errors were encountered: