XSD.exe generating unwanted string values in enum type instead of just the digit values specified in the file

Question

I have and xsd file that contains a enumerated type with options of 1 or 2. This is an extract of the file that contains the enum type CompanyCode

Running this file through xsd.exe /c test.xsd gives me a c# file that contains this code for the definition of the CompanyCode enum.

/// 
[System.CodeDom.Compiler.GeneratedCodeAttribute("xsd", "2.0.50727.3038")]
[System.SerializableAttribute()]
public enum CompanyCode {

    /// 
    [System.Xml.Serialization.XmlEnumAttribute("1")]
    Item1,

    /// 
    [System.Xml.Serialization.XmlEnumAttribute("2")]
    Item2,
}

Using this, when I read the data from the xml file, the values that come is the string Item1 or Item2, rather than the digits 1 or 2.

Should I just use a switch statement to convert the values to the 1 and 2 that I need to store in the destination, or is there a way I can get the xml file to read the 1 or 2 directly?

A typical record in the xml file looks like this


  DO NOT USE

Thanks

fenixil · Accepted Answer

I think you confused commentators by expression 'the values that come is the string Item1 or Item2'. In the example that you shared I can see that your main concern is that you cannot get 'xml value' from enum value:

var mLCCommodity = new MLCCommodity() { CompanyCode = CompanyCode.Item2 };
// below gives you 'Item2', but you just want '2'
var value = mLCCommodity.CompanyCode.ToString();

I see several ways to achieve what you need:

1. Quick, simple but risky

I checked that xsd.exe generates enum entries by convention appending xml value to the end of the enum entry so you can just remove Item from the value:

var quickCompanyCodeName = mLCCommodity.CompanyCode.ToString().Replace("Item",string.Empty);
Console.WriteLine(quickCompanyCodeName);

2. Slow, complex but less risky

You can read attribute from the enum item and get it's value. You still rely on the xsd.exe internals implying that it will always mark enum entries with this attribute, but I think that is much less risky than rely on the enum name construction convention. I used this answer to get attribute value:

var enumType = typeof(CompanyCode);
var memberInfos = enumType.GetMember(mLCCommodity.CompanyCode.ToString());
var enumValueMemberInfo = memberInfos.FirstOrDefault(m => m.DeclaringType == enumType);
var valueAttributes = enumValueMemberInfo.GetCustomAttributes(typeof(XmlEnumAttribute), false);
var companyCodeName = ((XmlEnumAttribute)valueAttributes[0]).Name;
Console.WriteLine(companyCodeName);

XSD.exe generating unwanted string values in enum type instead of just the digit values specified in the file

Answers (1)

1. Quick, simple but risky

2. Slow, complex but less risky

Related Questions