Publishing NuGet Packages Broken for RNW 0.62

[NickGerleman]

We see errors after the change from @tudorms about multiple copies of the ReactNativeWindows project in the universal solution.

Error parsing solution file at D:\a\1\s\vnext\ReactWindows-Universal.sln: Exception has been thrown by the target of an invocation. The solution file has two projects named "ReactWindowsCore". D:\a\1\s\vnext\ReactWindows-Universal.sln

https://dev.azure.com/ms/react-native-windows/_build/results?buildId=82226&view=results

Unsure of why this wasn't caught by PR validation. Possibly there is some setup difference or this was related to image changes?

[NickGerleman]

This likely only impacts RNW developers (or NuGet package consumers) instead of end-users.

[tudorms]

@asklar Do you have any ideas here? The file is identical to what we had in master when you did the change there.

[asklar]

@tudorms right - I think you might need #5012 but that might be too intrusive for a backport.
An easy fix would be to change the display name for one of the projects:
e.g. change:

Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "ReactWindowsCore", "ReactWindowsCore\ReactWindowsCore.vcxitems", "{11C084A3-A57C-4296-A679-CAC17B603145}"
EndProject
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "ReactWindowsCore", "ReactWindowsCore\ReactWindowsCore.vcxproj", "{11C084A3-A57C-4296-A679-CAC17B603144}"

into

Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "ReactWindowsCore-Items", "ReactWindowsCore\ReactWindowsCore.vcxitems", "{11C084A3-A57C-4296-A679-CAC17B603145}"
EndProject
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "ReactWindowsCore", "ReactWindowsCore\ReactWindowsCore.vcxproj", "{11C084A3-A57C-4296-A679-CAC17B603144}"

[tudorms]

So master branch publish was broken back then 3 weeks ago? I'm trying to figure out how we can catch something like this in the future.

[tudorms]

An easy fix would be to change the display name for one of the projects:

Visual Studio doesn't like that, it just reverts the change.