[Post-Event] April BucharestJS Meetup #21 | Building Node.JS Together (with Microsoft)

This week I had the opportunity to be invited by BucharestJS meetup to speak about Node.JS from Microsoft perspective.
It was a challenge for me - speaking about Microsoft in a front of Node.JS people is not an easy task. I was happy to survive after one afternoon with around 80 people with no mercy to Microsoft and Azure. I'm sure that a part of them will give a try to Visual Studio Code and/or Azure Services.

For me it was a pleasure to find people that were open to discover 'exotic' IDE and products. Thank you to all attendees that accepted for one hour to hear about Microsoft technologies.
More information related to session, slides, demos can be find below.

Title: Building Node.js Together
Abstract: JavaScript's simplicity, ubiquity, and event-driven paradigm, and its high performance runtimes like Microsoft's Chakra and Google's V8, have led it to spread beyond web pages and browsers to servers and clouds, IoT devices, mobile apps, and more via the Node.js platform. For years Microsoft has worked closely with industry and community partners to build and improve Node.js to meet developers' needs, from contributing Node's main system library years ago to driving better diagnostics today. In this session, learn a bit about the history of Node.js, why developers are so interested in it, and what's coming next from Microsoft and the open source project to address Node developers' needs.
Source code: https://github.com/vunvulear/BuildingNodeJSTogetherSampleAzureWebApp
Slides:

Building Node.js Together | Radu Vunvulea from Radu Vunvulea

Pictures

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 provi...

Cloud as a Story - Vunvulea Radu

Search This Blog