Suppose you have an enum type.
|
1 |
<span style="background: black none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;color:white;" > </span><span style="background: black none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;color:yellow;" >internal enum </span><span style="background: black none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; color: rgb(43, 145, 175);">SomeEnum <br /> </span><span style="background: black none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;color:white;" >{ <br /> SomeVeryDescriptiveName = 5<br /> } <br /></span> |
For some reason you want to use the name of the enum field as a string and not its value.
you can write:
Console.WriteLine(SomeEnum.SomeVeryDescriptiveName);
The output will be:
“SomeVeryDescriptiveName”
This is exactly what you wanted and every thing works fine.
But when you build the release version it doesn’t work.
So you debug it and of course under debug it works fine again.
Then you pull the heavy guns like the giants who walked on this earth long time ago taught you. Logging.
And than you find it:
When we build in release mode the assembly is obfuscated. This means that all internal and private names are mangled.
Since the enum is internal SomeEnum.SomeVeryDescriptiveName will become something like:
z.k and the output will be:
“k”
Thou shall not use strings!
