Asynchronous Master Class, May 18-19, Cluj-Napoca

In May we will have a great master class in Cluj-Napoca. Codecamp will bring Andrew Clymer and Richard Blewett to Cluj-Napoca. They will talk about asynchronous programming.

Registration link: http://codecamp-cluj-mai2013.eventbrite.com/

Toata lumea stie ca lucrul cu thread-uri nu este usor. Exista multe lucruri care pot sa mearga prost - problemele de concurenta sau de thread safe sunt la ordinea zilei. Codecamp doreste sa vina in ajutorul dezvoltatorilor din Cluj-Napoca cu un master class – Asynchronous Master Class. Acest master este in totalitate gratuit.
When: 18-19 Mai (full day’s event)
Where: Hotel Golden Tulip (Cluj-Napoca)
Cost: None
Master Class Title: Asynchronous Master Class
Trainers: Andrew Clymer and Richard Blewett
Abstract: The goal of the two days is to take people at various levels of asynchronous programming and show them a variety of programming styles, techniques to deliver modern asynchronous applications.
Topics: Tasks, Thread Safety, Concurrent Data Structures, Parallel Programming, Async and Await, Debugging asynchronous applications, Reactive framework

Toate persoanele care vor fi selectate pentru acest master class vor fi anuntate pe data de 14 Mai. Fiecare participant trebuie sa aibe asupra lui mailul de confirmare (printat). Accesul la acest master class se face pe baza acestuia.
Costurile acestui master class sunt suportate in totalitate de catre sponsorul acestui eveniment: iQuest

Registration link: http://codecamp-cluj-mai2013.eventbrite.com/

Comments

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

Cloud as a Story - Vunvulea Radu

Search This Blog