Variations in NuGet Package ID Case Sensitivity can lead to an Editor Restart Loop on Install

[ilexp]

Summary

In some rare cases, NuGet packages can have inconsistent naming, where package ID can differ in case sensitivity when retrieved / viewed on the web, vs. when downloaded and installed. To Duality, the installed package will then be a different one than the online package, causing an editor restart loop after installation.

How to reproduce

@SirePi initially reproduced this with an earlier version of the YAUI plugin by using the $id variable in the .nuspec, switching from CamelCase .Core to (derived from the .csproj) lowercase .core, triggering the issue.

Workaround

• As this could probably seen as an issue with changing a package ID after publishing, the workaround would be to simply not do that.

Analysis

• It seems NuGet is officially treating package IDs case-insensitive, though this seems to be very rarely relevant / used.
• Duality could work around this internally by using case-insensitive package ID comparison.
• Probably low priority for now.