Should RuntimeIdentifiers be updated to win-x instead of win7-x?

[mol]

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?

[amaitland]

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.

[mol]

Should I go ahead and create a pull request where I make this change for all projects?

[amaitland]

PR would be welcome. Otherwise I can have a look at what's required next week.

[amaitland]

Done in commits 1b5dd78 and 2bf01fa

[mol]

Oh, cool - thanks. I was otherwise going to look at it this weekend and create a PR :)