Skip to main content

.NET - Nice to have

By

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.
Labels:

Comments

  1. TudorNovember 8, 2011 at 6:34 PM

    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

By
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(
Post a Comment
Read more

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

By
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
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 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
Post a Comment
Read more