Open na1307 opened 5 months ago
Scottj1s
commented
4 months ago NETSDK1083: The specified RuntimeIdentifier is not recognized can often be mitigated by setting RuntimeIdentifiers explicitly in your project file (vs picking up defaults from .NET SDK or WinAppSDK targets files) and/or by setting the project property UseRidGraph to 'true'.
na1307
commented
4 months ago This happened during the "temporary project" build process, so doing that in my project doesn't fix it. The fundamental solution is to remove that RID from WinAppSdk.
Diegorro98
commented
3 months ago @Scottj1s Any update with this issue? It's a blocking issue for Dependabot because, even if WinAppSDK NuGet is up to date, it prevents other NuGets from being updated because Dependabot fails at checking updates and any other process if WinAppSDK is present.
I've read that the issue could be related to .NET CLI
Diegorro98
commented
1 week ago Seems to be working in latest versions of Windows App SDK (i.e. upgrading from 1.6.240821007-preview2 to 1.6.240829007) and no longer prevents other NuGets from being updated
Describe the bug
Microsoft.WindowsAppSDK update from dependabot fails with error NETSDK1083.
Steps to reproduce the bug
Set up dependabot in the GitHub repository and store the Windows App SDK project.
Expected behavior
dependabot should successfully update Microsoft.WindowsAppSDK.
Screenshots
No response
NuGet package version
None
Packaging type
No response
Windows version
No response
IDE
No response
Additional context
The PR that caused the problem is na1307/SimpleVHD#6. The dependabot log is here. If I remove EnableMsixTooling from the local and try to build, I get the same error.