I have a simple Enum
public enum TestEnum
TestOne = 3,
TestTwo = 4
var testing = TestEnum.TestOne;
Great question Mat.
The scenario of the question is this:
You have some unknown enum type and some unknown value of that type and you want to get the underlying numeric value of that unknown value.
This is the one-line way of doing this using reflection:
object underlyingValue = Convert.ChangeType(value, Enum.GetUnderlyingType(value.GetType()));
If value happens to be
value.GetType() would be equal to
Enum.GetUnderlyingType(value.GetType()) would be equal to
typeof(int) and value would be 3 (boxed; see http://msdn.microsoft.com/en-us/library/yz2be5wk.aspx for more details about boxing and unboxing values).
Why would one ever need to write such code? In my case, I have a routine that copies values from a viewmodel to a model. I use this in all my handlers in an ASP.NET MVC project as part of a very clean and elegant architecture for writing handlers that do not have the security problems the handlers generated by the Microsoft templates do.
The model is generated by the Entity Framework from the database and it contains a field of type int. The viewmodel has a field of some enum type, let's call it RecordStatus, which I have defined elsewhere in my project. I decided to support enums fully in my framework. But now there is a mismatch between the type of the field in the model and the type of the corresponding field in the viewmodel. My code detects this and converts the enum to an int using the code similar to the one-liner given above.