Want to learn about the latest and greatest in the 64-bit Visual Studio 2022? Join Scott Hanselman and Visual Studio product team as they take Visual Studio 2022 for a spin.

20:27 Profiling .NET apps in Visual Studio 2022 

23:19 Cross platform apps with WSL and CMake in Visual Studio 2022 

26:07 Testing your .NET app on Linux 

28:00 Easily create CI/CD pipelines using GitHub actions with Visual Studio  2022

30:40 Balloon drop! 

Today, we are launching .NET Live TV, your one stop shop for all .NET and Visual Studio live streams across Twitch and YouTube. We are always looking for new ways to bring great content to the developer community and innovate in ways to interact with you in real-time. Live streaming gives us the opportunity to deliver more content where everyone can ask questions and interact with the product teams. 

Query Store is enabled by default in SQL Server 2022 

Announcing SqlKata an Elegant Sql Query Builder for C# 

Entity Framework (EF) Core is the rearchitected and rewritten version of the Entity Framework object relational mapping engine for .NET Core applications. It is very light-weight, extensible, and cross platform.

However, high transaction .NET Core applications using EF Core face performance and scalability bottlenecks in the database-tier under peak loads. This is because, although you can linearly scale the application tier by adding more application servers, you cannot add more database servers to scale it.

But, if you use a distributed cache like NCache in your .NET Core applications, you can quickly remove these performance and scalability bottlenecks and handle extreme transaction loads. 

• An error occurred while generating the SSH keys. Please check that the environment is properly configured. Details: cat: /Users/cc/Library/Caches/Xamarin/XMA/Keys/1984b83a-dde9-4031-919d-b1d1b8411d0d: No such file or directory
• InvalidOperationException while debugging Xamarin Forms app
• Frame note in module in Xamarin Forms Android
• Internal compiler error is fixed and analysis for WDK completes as usual.
• We fixed an issue in the new Find in Files experience where hidden files and auto-generated files were not searchable.
• Fixed issue with deployment of UWP apps to remote machines where deployment fails with message "DEP0600: Deployment failed. DkmException - Error in the application."
• Local static variable not initialized in inlined function of class imported from dll
• VS 2019 16.5.X: Multiple startup projects while Live Visual Tree was last opened in a debug session crashes
• Fixed issues where for the C++ formatting indentation of new lines with only ending parenthesis.
• Fixed a bug preventing some users from installing 16.5
• Fix an issue where Visual Studio can crash when the display configuration changes.
• Fixed an issue causing slow downs when opening solutions that are impacting the IntelliSense code and related operations.
• Fixed a crash with the debugger that users can run into when the target application being debugged raises an exception.
• Added support for Xcode 11.4.

Improved the MSBuild selection logic. The standalone instance inside OmniSharp is now preferred over VS2017, with VS2019 given the highest priority. This ensures that .NET Core 3.0 works correctly. It is also possible manually provide an MSBuild path using OmniSharp configuration, which is then always selected. (omnisharp-roslyn#1541, PR: omnisharp-roslyn#1545)

    {
        "MSBuild": {
            "MSBuildOverride": {
                "MSBuildPath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\Enterprise\\MSBuild\\15.0\\Bin",
                "Name": "vs2017 msbuild"
            }
        }
    }

In this article I will explain some general purpose queries. I think each developer should have knowledge of these queries. These queries are not related to any specific topic of SQL. But knowledge of such queries can solve some complex tasks and may be used in many scenarios, so I decided to write an article on these queries.