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
It's the same behavior as the VS internal resource editor. Any deviation from the default behavior may result in inconsistencies.
Dropping the <value> element is not an option, since then it won't compile any longer. (Error MSB3103 Invalid Resx file. System.NotImplementedException: User-facing error for bad resx that has child elements but not value)
Tried to apply xsi:nil, but that didn't work either.
Strange, when I remove the <value> it compiles but the Visual Studio Resource Editor fails. But you are right, only removing the <value> node is not a good idea.
With a German <value> node:
After removing the <value> node:
The Visual Studio Resource Editor shows an exception:
Delete the German string for "Yes" with the ResX Manager.
Works well for entries without a comment. The ResX Manager deletes the
<data>
node:But when the German stings has a comment the string is set to an empty string:
deleting of "Ja" results in:
In this case the fallback mechanism of the resource manager does not work, because the string is an empty string but it should be
null
.The text was updated successfully, but these errors were encountered: