Here’s a summary of what’s new in this preview release:

• Improved ASP.NET Core debugging experience
• Servers & middleware
  • IHttpSysRequestTimingFeature
  • SNI hostname in ITlsHandshakeFeature
  • IExceptionHandler
• Blazor
  • New Blazor Web App project template
  • Blazor router integration with endpoint routing
  • Enable interactivity for individual components with Blazor Server
  • Improved packaging of Webcil files
  • Blazor Content Security Policy (CSP) compatibility
• API authoring
  • Support for generic attributes
• SignalR
  • SignalR seamless reconnect
• Native AOT
  • Support for AsParameters and automatic metadata generation in compile-timed generated minimal APIs
• Authentication and authorization
  • Authentication updates in ASP.NET Core SPA templates
  • New analyzer for recommended AuthorizationBuilder usage
   

Vertical Slice Architecture, not Layers! 

Why Vertical Slice Architecture? Nobody wants to deal with a system that is hard to change and easy to introduce bugs because it's a spaghetti code mess of various technical concerns. Clean Architecture is popular because it separates concerns into many different layers. But why are we organizing code by layers? Does adding a new feature require you to modify files across multiple projects in your UI, business, and data access layers? Vertical Slice Architecture is about how you organize code and focus on features instead of technical layers will make your system easier to change. 

Add command 'listRemoteDockerProcess' and variable 'pickRemoteDockerProcess' (#4607, PR: #4617)
Ensure we only start one instance of OmniSharp server (PR: #4612)
Update OmniSharp version to 1.37.11
  Include timing info in logged responses (PR: omnisharp-roslyn#2173)
  Defend against null value in BuildErrorEventArgs (omnisharp-roslyn#2171, PR: omnisharp-roslyn#2172)
  Updated to all the latest .NET SDKs (PR: omnisharp-roslyn#2166)
  Add support for GoToDefinition on source-generated files (PR: omnisharp-roslyn#2170)
  Add V2 version of GotoDefinitionService (PR: omnisharp-roslyn#2168)
  avoid NRE when document is null (PR: omnisharp-roslyn#2163))

 

These are the issues addressed in 15.9.15:

• Updated signing of VC Redist packages to enable continued deployment on Windows XP. This fix may have an increased chance of requiring a reboot of the machine in order to install an updated VC++ Redistributable package.
• Fixed in issue where GoToDefinition does not work for JavaScript in script blocks of cshtml files.
• Calling pmr monotonic_buffer_resource release will corrupt memory.
• Fix for HRESULT E_FAIL build error in some C++ projects when upgrading to 15.9.13

Security Advisory Notices

• Git for Visual Studio Elevation of Privilege Vulnerability 

These are the customer-reported issues addressed in 15.9.9:

• SSDT: We fixed a crash in the SSIS Foreach Loop container.
• A few .NET native for UWP customer issues were fixed in .NET native tools 2.2 (UWP 6.2.4).
• We have corrected dual signing of Visual C++ Redistributable installers.

Security Advisory Notices

• A remote code execution vulnerability exists when the Visual Studio C++ Redistributable Installer improperly validates input before loading dynamic link library (DLL) files.
• Unity Editor Remote Code Execution Vulnerability.
• .NET Core NuGet Tampering Vulnerability. 

J (J language) is a high-level, general-purpose, high-performance programming language. J is portable and runs on 32/64-bit Windows/Linux/Mac as well as iOS, Android, and other platforms. J source (required only if Jsoftware binaries don't meet your requirements) is available under both commercial and GPL 3 license. J systems can be installed and distributed for free.

J systems have:

• an integrated development environment
• standard libraries, utilities, and packages
• console, browser, and Qt front ends
• interfaces with other programming languages and applications
• integrated graphics
• memory mapped files for high performance data applications
• Jd