Page referred to: https://learn.microsoft.com/en-us/windows/apps/get-started/start-here
When installing Windows SDKs for the first time, the PATH entries to the SDK components are set. It may require reopening Visual Studio or a system restart for them to be fully updated and available. Building/debugging will fail unless this happens.
A user reported an issue getting a WinUI 3 project started after following the WinGet instructions on the page, and I suspect that the PATH issue was behind it. See: microsoft/PowerToys#47644
I think it would therefore be useful to add a call-out in the instructions here to recommend a reboot if the user experiences issues compiling or running the test application.
References:
https://learn.microsoft.com/en-us/answers/questions/1184941/the-sdk-microsoft-net-sdk-specified-could-not-be-f
https://stackoverflow.com/questions/63746838/net-sdks-not-installing-correctly/66128116#66128116
Page referred to: https://learn.microsoft.com/en-us/windows/apps/get-started/start-here
When installing Windows SDKs for the first time, the PATH entries to the SDK components are set. It may require reopening Visual Studio or a system restart for them to be fully updated and available. Building/debugging will fail unless this happens.
A user reported an issue getting a WinUI 3 project started after following the WinGet instructions on the page, and I suspect that the PATH issue was behind it. See: microsoft/PowerToys#47644
I think it would therefore be useful to add a call-out in the instructions here to recommend a reboot if the user experiences issues compiling or running the test application.
References:
https://learn.microsoft.com/en-us/answers/questions/1184941/the-sdk-microsoft-net-sdk-specified-could-not-be-f
https://stackoverflow.com/questions/63746838/net-sdks-not-installing-correctly/66128116#66128116