Skip to main content

[Event] Global Windows Azure Bootcamp in Cluj-Napoca, March 29

Registration link: https://codecamp-cluj-azurebootcamp.eventbrite.com

One year ago Codecamp Romania added Cluj-Napoca on the map when we organized Global Windows Azure BootCamp, we here part of an event organized in more than 90 location worldwide.

This year, we are doing the same thing. In March 29 we will organize in Cluj-Napoca a full day of workshops related to Windows Azure. This event is part of Global Windows Azure Bootcamp, which is organized in more 140 locations registered in 56 countries.

Let’s see what will happen in Cluj-Napoca. In March 29, there will be workshops of 90 minutes, where all the attendees will have the opportunity to learn how to use different services that are available on Windows Azure. Because of this you should bring your own laptop with you and have Visual Studio 2013 or 2012, Windows Azure SDK and a free account for Windows Azure set.

The event will start at 9:00 AM with a little networking. The real coding will start at 9:30 AM with a workshop about how to deploy and hosts web sites on Windows Azure. After this we will continue with a training related to different ways how data can be persisted on Windows Azure. At the end we will try to see and understand what are the different mechanism (ways) of creating batches jobs on Windows Azure.

Registration link: https://codecamp-cluj-azurebootcamp.eventbrite.com

And don’t forget, this event is 100% free. Special thanks to our sponsors:

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