Replies: 1 comment 3 replies
-
I don't remember if there was a specific reason for this, quick look at the change log and nothing stands out. Changing from win 7 makes sense. Long as nothing breaks happy to switch to the more generic identifier. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In CefSharp.BrowserSubprocess.csproj the RuntimeIdentifiers are listed as
<RuntimeIdentifiers>win7-x86;win7-x64</RuntimeIdentifiers>
This caused some issues with code I have that is doing a x64 build, because the default then is to use a
win-x64
identifier.There are other projects with the same identifiers. Perhaps those should all be updated to
<RuntimeIdentifiers>win-x86;win-x64</RuntimeIdentifiers>
, when Windows 7 is anyway no longer supported?Beta Was this translation helpful? Give feedback.
All reactions