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
When using win10-x64 (or win10-x86), an error is thrown during build:
Error: C:\Users\runneradmin\AppData\Local\Microsoft\dotnet\sdk\8.0.101\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(90,5): error NETSDK1083: The specified RuntimeIdentifier 'win10-x64' is not recognized. See https://aka.ms/netsdk1083 for more information. [D:\a\maui-samples\maui-samples\8.0\Apps\WeatherTwentyOne\src\WeatherTwentyOne\WeatherTwentyOne.csproj::TargetFramework=net8.0-maccatalyst]
win-x64 should be used instead. This allows the build to be successfully completed. However, I will note that the produced build fails to start.
BurkusCat
changed the title
-p:RuntimeIdentifierOverride=win10-x64 throws an error on .NET8
-p:RuntimeIdentifierOverride=win10-x64 throws an error on .NET8 (unpackaged CLI)
Feb 2, 2024
I think potentially, everything to do with RuntimeIdentifier and RuntimeIdentifierOverride is actually outdated and is no longer required in .NET 8. I've created a PR for the MAUI samples repo where I demonstrate working packaged and unpackaged GitHub actions pipelines without any of the RuntimeIdentifier workaround stuff: dotnet/maui-samples#442
I think it would make things simpler and avoid errors like in my originally reported documentation issue.
Type of issue
Outdated article
Description
When using
win10-x64
(orwin10-x86
), an error is thrown during build:win-x64
should be used instead. This allows the build to be successfully completed. However, I will note that the produced build fails to start.Page URL
https://learn.microsoft.com/en-us/dotnet/maui/windows/deployment/publish-unpackaged-cli?view=net-maui-8.0
Content source URL
https://github.com/dotnet/docs-maui/blob/main/docs/windows/deployment/publish-unpackaged-cli.md
Document Version Independent Id
912ce2ed-fd27-02ad-d94a-eed9ed756d59
Article author
@davidbritch
Metadata
The text was updated successfully, but these errors were encountered: