Skip to main content

Post event - Intâlnire CodeCamp la Cluj-Napoca - 24 martie 2012


Ieri, 24 martie 2012, a avut loc un nou eveniment de primavara pentru comunitate. Acesta a fost organizat de catre CodeCamp in Cluj-Napoca. Fata de alte evenimente CodeCamp pe care le-am organizat in Cluj, acesta a fost cel mare de pana acuma (peste 115 persoane). Speram ca si in viitor sa avem acelasi numar de participant. Pe aceasta cale vreau sa le multumesc tuturor pentru participare.
Au fost 5 prezentari foarte interesante despre diferite subiecte.
Mihai Nadăș - Globally distributed DNS service with Windows Azure's Traffic Manager
Florin Coros - Good Unit Tests Ask For Quality Code
Radu Vunvulea - ASP.NET MVC 3 - Bad practices
Levente Veres - How to create easily Workflows and present with Visio in SharePoint 2010
Mihai Tataran -    
Building elastic, autoscalable solutions with Windows Azure
Daca in viitor doriti sa tineti prezentari in Cluj-Napoca si nu numai, va rog sa ma contactati.
 
As vrea sa le multumesc sponsoriilor ca ne-au ajutat sa organizam acest eveniment. Pe langa o locatie si o masa excelenta am avut parte si de multe premii oferite de catre sponsori.

Gazda evenimentului:
   SoftVision
Sponsori:
Yonder          iQuest

Mai jos puteti sa gasiti cateva poze de la acest eveniment

12, 3, 4, 5, 6, 7, 8, 9

In cadrui acestui eveniment am tinut o prezentare cu titlul: ASP.NET MVC 3 - Bad practice pe care o puteti gasi  mai jos.

Multumim tuturor pentru participare si ne vedem in mai la ITCamp.
Link spre anuntul evenimentului

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