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
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.
Duality could work around this internally by using case-insensitive package ID comparison.
Probably low priority for now.
The text was updated successfully, but these errors were encountered:
ilexp
added
Bug
It's broken and should be fixed
Editor
Area: Duality editor or support libraries
Nice2Have
Beneficial, but only very slightly so
labels
Dec 9, 2018
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
Analysis
The text was updated successfully, but these errors were encountered: