Language Lassi

Hi there! My name is Hassan Habib, I’m a Sr. Engineering Manager @ Microsoft. This is my very first blog post on the ASP.NET team blog. You may know me from my OData posts . Few weeks ago I reached out to Daniel Roth wondering if it would be a good idea to share how Microsoft engineers use Microsoft products to build our own systems. It’s a little something we call “Run Microsoft on Microsoft” – Daniel was very supportive and we worked together to make it possible, and for that I’m very grateful. As I continue to work with internal teams inside Microsoft to develop end-to-end enterprise solutions, my experiences with Microsoft technologies continue to evolve into so many different directions. These experiences I thought they might be useful for all the engineers out there to see what it’s like to bring Microsoft technologies into perspective when it comes to building real-life end to end products. In my blog posts I will try to bring you that perspective, how Microsoft engineers leve

We’re excited to announce updates to the F# tools for Visual Studio 16.10. For this release, we’re continuing our trend of improving the F# experience in Visual Studio to build upon what was released in the VS 16.9 update last February . Support for Go to Definition on external symbols Better support for mixing C# and F# projects in a solution More quick fixes and refactorings More tooling performance and responsiveness improvements More core compiler improvements Let’s dive in! Go to Definition on external symbols This one’s been a long time coming. We’ve had a feature request since 2016 and several trial implementations throughout the years. Now it’s here! As shown in the video, you can either use the f12 key or ctrl+click to navigate to a declaration, just like in source code in your own solution. When you navigate, Visual Studio generates a complete F# Signature File that represents the module or namespace that the symbol lives under, with XML documentation if it i

Curriculum for the course 🎮 Easy JavaScript Game Development with Kaboom.js (Mario, Zelda, and Space Invaders) - Full Course Learn how use JavaScript and Kaboom.js to create three classic video games. You will create games similar to Space Invaders, Super Mario Bros. and Legend of Zelda. Kaboom.js makes makes it easier and quicker to create games. ✏️ This course was developed by Ania Kubów. Check out her channel: https://www.youtube.com/c/AniaKubów ⭐️ Code ⭐️ 🔗 Space Invaders: https://replit.com/@AniaKubow/Kaboomjs-Space-Invaders 🔗 Mario: https://replit.com/@AniaKubow/Kaboomjs-Mario 🔗 Zelda: https://replit.com/@AniaKubow/Kaboomjs-Zelda ⭐️ Course Contents ⭐️ ⌨️ (0:00:00) Introduction ⌨️ (0:04:12) The basics ⌨️ (0:16:47) Space Invaders ⌨️ (0:47:32) Mario ⌨️ (1:45:15) Zelda ⌨️ (2:46:39) Sharing to the Replit App Store ⌨️ (2:48:03) Using any Code Editor 🎉 Thanks to Replit for providing a grant that made this course possible. -- Learn to code for free and get a developer job:

Today, we are releasing the May 2021 Cumulative Update Preview for .NET Framework. Quality and Reliability This release contains the following quality and reliability improvements. CLR 1 Addresses a performance issue caused by incorrect configuration in the GC. Addresses an issue where a background GC could pause the runtime for a long period of time if a large managed heap is filled with long lived objects with a deep chain of references. Addresses an issue where crashes could occur if security stackwalks were generated during ThreadAbortException handling. NCL 2 .NET Framework 4.8 will now allow to negotiate TLS 1.3 if underlying OS supports it. WPF 3 Addresses an issue when rapid typing using an IME can crash via FailFast. Addresses an issue where Thaana characters displayed in left-to-right order. Addresses a crash when WebBrowser receives a completion event for a navigation it tried to cancel. 1 Common Language Runtime (CLR) 2 Network Class Library (NCL) 3 Wi

.NET 6 Preview 4 is now available and includes many great new improvements to ASP.NET Core. Here’s what’s new in this preview release: Introducing minimal APIs Async streaming HTTP logging middleware Use Kestrel for the default launch profile in new projects IConnectionSocketFeature Improved single-page app (SPA) templates .NET Hot Reload updates Generic type constraints in Razor components Blazor error boundaries Blazor WebAssembly ahead-of-time (AOT) compilation .NET MAUI Blazor apps Other performance improvements Get started To get started with ASP.NET Core in .NET 6 Preview 4, install the .NET 6 SDK . If you’re on Windows using Visual Studio, we recommend installing the latest preview of Visual Studio 2019 16.11 . If you’re on macOS, we recommend installing the latest preview of Visual Studio 2019 for Mac 8.10 . Upgrade an existing project To upgrade an existing ASP.NET Core app from .NET 6 Preview 3 to .NET 6 Preview 4: Update all Microsoft.AspNetCore.* pack

Today, the Entity Framework Core team announces the fourth preview release of EF Core 6.0. The main theme of this release is performance – and we’ll concentrate on that below – details on getting EF Core 6.0 preview 4 are at the end of this blog post. The short and sweet summary: EF Core 6.0 performance is now 70% faster on the industry-standard TechEmpower Fortunes benchmark, compared to 5.0. This is the full-stack perf improvement, including improvements in the benchmark code, the .NET runtime, etc. EF Core 6.0 itself is 31% faster executing queries. Heap allocations have been reduced by 43% . The runtime perf push When the EF Core team started the planning process for version 6.0, we knew it was finally time to address an important area. After several years spent delivering new EF Core features, stabilizing the product and progressively narrowing the feature gap with previous versions of Entity Framework, we wanted to put an emphasis on performance and to see exactly where