[PostEvent] ITCamp 2014, Cluj-Napoca

Last week, Cluj-Napoca hosted the 4th edition of ITCamp. More than 400 people participate to this premium conference. During the two days of the event, more than 30 speakers talked about Microsoft Stack, Architecture, Cloud, Development methodology and many more. For this two days we could say that Cluj-Napoca was the center of IT from Romania.
This was the first year when we had 4 tracks in parallel and there were moments where it was pretty hard to decide at which session to attend. Session like “Management of Fear”, “30 Tools for Modern .NET Web Development in 60 minutes”, “Code Quality through Application Software Infrastructure” or “The Battle for Success” made waves between attendees.
Special thanks to the core organization team (Mihai Tataran and Tudy-Tudor Damian). You made a great job this year. There were a lot of sponsors that sustained this event. I’m proud that iQuest was one of the Platinum sponsors.
This year I had the opportunity to do a workshop dedicate to Agile, oriented to practice. The main purpose of it was to see how we can resolve different issues that can appear in a team or company using Agile methodology (if is possible). Also, in the first day of the event I had a session related to redundancy over Microsoft Azure - Database and Public Endpoints redundancy on Azure. Even if we are on a cloud platform, we need to think on different solutions that would offer us redundancy and failover mechanism. Cloud is not managed by God.
ITCamp 2014 Summary: 400+ people, 34 speakers, 2 days, 4 workshops, 4 tracks, 28 sponsors, 6 media partners and a lot of good sessions.
See you next year!

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