Skip to main content

[Post Event] Global Azure Bootcamp in Cluj-Napoca, April 25, 2015 - Cluj-Napoca

The 3rd edition of Global Azure Bootcamp finished with success in Cluj-Napoca. We had a full day dedicated to Azure and IoT.
At this edition we talked about Event Hub, Stream Analytics, Active Geo-Replication over SQL Azure and we discover how we can create our own datacenter in Azure. All these technologies help us to provider better solution with less development, cost and a higher quality rate.
Thank you cloud! Thank you Azure! Thank you Microsoft!

The event from Cluj-Napoca was organized by ITCamp and was sustained by two great company companies from Cluj-Napoca (RIA Solutions and ISDC). Without our local sponsors this event  would not have been possible.
Thank you RIA Solutions! Thank you ISDC!

In the end we would like to  thank you to all 50 participants that joined this event and sacrificed a beautiful and shiny Saturday for Azure.
Thank you all!

All the attendees that filled the survey at the end of the event had a chance to win one of the licences offered by our global sponsors.
So, ... the winners are:
  • Jetbrains License: Cosmin Vana
  • myget: Dan Dobocan
  • Blue Syntax: Erno Lazar
  • Opsgility: Cristian Cojita
  • Opsgility: Faur Flaviu
  • Opsgility: Dragos Vlad
Labs Resources: https://onedrive.live.com/?cid=bb7d9f52e4fdb024&id=bb7d9f52e4fdb024%21160588&ithint=folder,&authkey=!AFpKtgZjQooCU5U
Pictures from event:

  


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