Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dependabot fails to update Microsoft.WindowsAppSDK version #4387

Open
na1307 opened this issue May 3, 2024 · 2 comments
Open

dependabot fails to update Microsoft.WindowsAppSDK version #4387

na1307 opened this issue May 3, 2024 · 2 comments
Labels
area-DeveloperTools Issues related to authoring (source and IDL), debugging, HotReload, LiveVisualTree, VS integration

Comments

@na1307
Copy link

na1307 commented May 3, 2024

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.

@codendone codendone added the area-DeveloperTools Issues related to authoring (source and IDL), debugging, HotReload, LiveVisualTree, VS integration label May 9, 2024
@Scottj1s
Copy link
Member

Scottj1s commented May 9, 2024

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
Copy link
Author

na1307 commented May 9, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-DeveloperTools Issues related to authoring (source and IDL), debugging, HotReload, LiveVisualTree, VS integration
Projects
None yet
Development

No branches or pull requests

3 participants