Skip to main content

Adnotare enum cu mai multe valori

Cand dorim sa serializam un enum putem sa atasam la valoarea fiecarui item din enum atributul XmlEnumAttribute. Astfel la serializare/deserializare o sa putem lucra cu o valoarea string nu cu o valoare numerica.
Pana aici nici o problema, dar cum facem sa obtinem doar aceasta valoarea si nu un xml care contine si aceasta valoarea . De exemplu pentru enum-ul:
public enum Dimension
{
[XmlEnum(Name="BigT")]
Big
[XmlEnum(Name="SmallT")]
Small
}

am obține folosindu-ne de XmlSerializer un output care contine si un nod care specifica ce tip de data ii. Pentru a putea sa obtinem doar valoare BigT sau SmallT putem sa apelam la reflection si sa iteram prin atributele item-ului respectiv pana ajungem la un atribut de tip XmlEnumAttribute.
Acuma, daca ducem problema umpic mai departe, putem sa ajungem la cazuri in care elementele din enum au diferite valori. De exemplu daca lucram cu doua sau mai multe aplicații, putem sa avem doua sau mai multe reprezentări pentru aceiasi valoare. De exemplu o aplicație poate sa isi noteze valoare Big cu BigT, iar alta cu BigState. La prima strigare putem sa scriem un swith, iar in funcție de sistemul de unde preluam sau trimitem date sa avem o anumita valoare.
O solutie mai generala este sa scriem doua metode care sa stie sa convertească un string intr-un enum in functie de valoarea atributelor cu care adnotam un anumit item din enum. De exemplu in exemplul dat mai sus putem sa avem:
public enum Dimension
{
[FirstSystem("BigT")]
[SecondSystem("BigState")]
Big
[FirstSystem(Name="SmallT")]
[SecondSystem("SmallState")]
Small
}
In felul acesta, putem sa avem oricate valori pentru un anum. Atributele custom pe care le-am definit trebuie sa mosteneasca din clasa XmlEnumAttribute. Se poate scrie si un atribut custom, dar am folosit aceasta clasa deoarece deja continea o valoare de tip string.
Mai jos gasiti doua metode care ne permit sa convertim un enum in string si viceversa pe baza atributelor. Pentru a putea obtine valorea unui atribut este nevoie sa iteram prin toata lista de atribute pana ajungem la atributul pe care noi il dorim.
 public static string GetAttributeValue<TAttribute>(Enum @enum)
where TAttribute: XmlEnumAttribute
{
Type enumType = @enum.GetType();
Type attributeType = typeof (TAttribute);
FieldInfo info = enumType.GetField(@enum.ToString("G"));
if (!info.IsDefined(typeof(XmlEnumAttribute), false))
{
return @enum.ToString("G");
}

foreach (var customAttribute in info.GetCustomAttributes(attributeType, false))
{
if (customAttribute.GetType() == attributeType)
{
XmlEnumAttribute attribute = (XmlEnumAttribute)customAttribute;
return attribute.Name;
}
}

throw new Exception("The given attribute could not be found.");
}


public static TEnum GetEnumByAttributeValue<TEnum,TAttribute>(string value)
where TAttribute: XmlEnumAttribute
{
Type enumType = typeof(TEnum);

foreach (var item in Enum.GetValues(enumType))
{
if(GetAttributeValue<TAttribute>((Enum)item)==value)
{
return (TEnum)Enum.Parse(enumType, item.ToString());
}
}

throw new IndexOutOfRangeException(string.Format("The {0} attribute value cannot be found on the {1} enum", value, enumType.Name));
}

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too