Skip to main content

.NET - Nice to have

In C# la crearea unui obiect putem sa inițializam propietatiile acestuia prin următoarea sintaxa:

Engine engine=new Engine(…)
{
Power = 101,
Type = “ES12RW120TDI”
};
Am simtit uneori nevoie sa pot face acelasi lucre si cu un obiect deja creat. Exista locuri cand obiectul este initalizat de un factory sau deja exista, si trebuie sa schimbam valoarea unor proprietati. Mi-ar placea sa pot face urmatorul lucru:
Engine engine = InitEngine(…)
{
Power = 101,
Type = “ES12RW120TDI”
};
sau
use (engine)
{
Power = 101,
Type = “ES12RW120TDI”
};
In loc de
engine.Power = 101;
engine.Type = “ES12RW120TDI”;
Nu cred ca o sa vad vreodată acest feature si nici din punct de vedere a unui limbaj de programare sintaxa nu este tocmai corecta, dar ar fi nice to have, uneori ne-ar putea usura putin codul.

Comments

  1. Treci la VB http://msdn.microsoft.com/en-us/library/wc500chb.aspx :-D

    Ce as fi vrut eu la chestia asta este sa poti sa bagi si eventuri acolo. E aiurea un cod care arata asa:
    var x=new X {
    A='a',
    B='b'
    };
    x.E+=e;
    x.F+=f;

    ReplyDelete
  2. Exact - in VB(.Net) exista dintotdeauna asa ceva, dar e mai mult un sintactic sugar care face codul sa arate ciudat..

    In 3 ani de zile de folosit VB am evitat with in general - in primul rand fiindca with in VB permitea cod arbitrar in interior, si se ajungea la carnatzi de 50 de linii in care nu mai stiai de ce obiect tine un property, de genul:
    With alertLabel
    If value = 0 Then
    .ForeColor = draw.Color.Red
    .Font = New draw.Font(.Font, draw.FontStyle.Bold Or draw.FontStyle.Italic)
    Else
    .Forecolor = draw.Color.Black
    .Font = New draw.Font(.Font, draw.FontStyle.Regular)
    End If
    End With

    ReplyDelete

Post a Comment

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