Skip to main content

Luni 09.04.2012 - Emisiune live despre Windows Azure

Luni, 09.04.2012, am fost invitat sa particip la un TeckTalk de catre comunitatea ITSpark. In cadrul acestei emisiune o sa discutam despre Windows Azure. Mai jos gasiti subiectele pe care o sa le abordam in cadrul emisiunii:
  • Windows Azure - overview
  • Componentele Windows Azure
  • Azure Development do-s and don't-s
O sa incercam sa discutam si despre bunele practici in dezvoltarea aplicatiilor pe aceasta platforma.
Emisiunea se va trasmite LIVE de la ora 18:00 la urmatoarea adresa http://live.itspark.ro/. In cadrul emisiunii puteti sa ne puneti orice intrebare legata de acest subiect. In cazul in care nu puteti sa ne urmariti live, puteti oricand sa urmariti emisiunea la urmatorea adresa http://itspark.ro/w/wiki/2012-04-09-itspark-techtalk-episodul-10.aspx.
Sa nu uitati ca vizionarea acestei emisiuni este GRATIS atat in versiune live cat si offline. Ne vedem luni de la ora 18:00.

UPDATE: La urmatoarea adresa puteti sa urmariti emisiune offline http://vimeo.com/channels/itspark#40531023

Comments

  1. Mi-am pus un reminder si sper sa va vad live. Am vazut-o si pe Steliana in episodul 9.

    ReplyDelete
  2. Te asteptam luni intr-un nou episod.

    ReplyDelete

Post a Comment

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