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(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP