The function used to return "TrueString" or "FalseString" back then. Nowadays it returns "True" or "False".
Re:I don’t know how to create a website
by MaxBarraclough on Monday July 09, 2018 @08:22AM
(#17489685)
Aren't those identical? If I understand correctly, .Net guarantees string internment for all string literals, even across assembly boundaries, so they should end up referring to the same String instances.
https://blog.jetbrains.com/dotnet/2015/02/12/string-internin...
It's not a matter of instance or memory. In the aforementioned example it was me trying to print valid JSON from a razor view, so the capital T in "True", was causing me headaches. I wouldn't of course use "toLower" as a workaround and actually found out the best practice. However this incident made me curious regarding this behavior and triggered my little "research".
Re:I don’t know how to create a website
by MaxBarraclough on Tuesday July 10, 2018 @04:32AM
(#17496279)
I don't follow. Boolean.TrueString is "True", with a capital 'T'. I don't see that anything on SO is out of date.
The StackOverflowers note that the implementation technically doesn't match the spec, but in a way which can only be observed by using reflection https://stackoverflow.com/questions/491334#comment34617036_4...
The correct solution remains `b ? "true" : "false"`, no?
If the XML spec requires exactly those strings, why do anything cute with `ToString`?