Using C# 8.0 in Core 2.x, .NET Framework and UWP projects 

What's new in this release?

• Full C#7.0 support
• .NET Core support

Today is the official GA release for .NET 5, and along with it we are excited to share the latest updates with our recent release of C#/WinRT version 1.0. C#/WinRT provides WinRT projection support for .NET 5 based apps. The Windows SDK leverages this technology and is now integrated with the .NET 5.0 SDK to expose Windows APIs through the new Target Framework Monikers. In addition to the Windows SDK support added for .NET 5, C#/WinRT itself allows component authors to build their own .NET 5 projections using the CsWinRT NuGet package.  

These are the customer-reported issues addressed in 15.7.1:

• This release includes a fix that reduces memory usage and GC pressure during solution load.

Microsoft Security Advisory for .NET Core Denial Of Service Vulnerability

CVE-2018-0765

Microsoft is releasing this security advisory to provide information about a vulnerability in .NET Core and .NET native version 2.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.

Microsoft is aware of a denial of service vulnerability that exists when .NET Framework and .NET Core improperly process XML documents. An attacker who successfully exploited this vulnerability could cause a denial of service against a .NET Framework, .NET Core, or .NET native application.

The update addresses the vulnerability by correcting how .NET Framework, .NET Core, and .NET native applications handle XML document processing.

If your application is an ASP.NET Core application, developers are also advised to update to ASP.NET Core 2.0.8. 

Added initial support for C# 8. 

his is the last preview for .NET 7 and the next version will be our first release candidate (RC). 

What's the big deal with IAsyncEnumerable<T> in .NET Core 3.0? 

[HttpGet]
public IAsyncEnumerable<Product> Get()
    => productsRepository.GetAllProducts();

Team Explorer support for TLSv1.2

• We have updated the Git and the Git Credential Manager components that ship in Visual Studio.
• The optional Git for Windows component has also been updated.
• This update allows Git to connect to services that have deprecated support for TLSv1 and TLSv1.1 in favor of TLSv1.2.

Issues Fixed in this Release

These are the customer-reported issues addressed in this release:

• Projects targeting .NET Core 2.1 or newer are not supported by Visual Studio 2017 version 15.5.
• Fixed issue where installation of the SDK for .NET Core 2.1 or newer would cause the option to create ASP.NET Core 2.0 Web applications to disappear. 

var numbers1_CS11 = new[] { 1, 2, 3 };

var numbers1_CS_11 = new int[] { 1, 2, 3 };

int[] numbers1_CS12 = [ 1, 2, 3 ];

error CS9176: There is no target type for the collection expression.

Span<string> span1_CS11 = new string[] { "AC", "AL" };

Span<string> span1_CS12 = [ "AC", "AL" ];

ReadOnlySpan<string> readOnlySpan_CS12 = [ "Africa",  "Asia", "Europa"];

int[][] array2D_CS11 =
  {
    new int[] { 2002, 2006, 2010},
    new int[] { 2014, 2018},
    new int[] { 2022, 2026, 2030}
  };

int[][] array2D_CS12 =
  [
     [2002, 2006, 2010],
     [2014, 2018],
     [2022, 2026, 2030]
  ];

List<string> list_CS11 = new List<string> { "Item 1", "Item 2" };

List<string> list_CS12 = [ "Item 1", "Item 2" ];

// Before C#12
List<User> users = new List<User>();
// or
var users = new List<User>();
// or
List<User> user = new();

// C#12
List<User> users = [];

int[] numbers1_CS12 = [ 1, 2, 3 ];
int[] numbers2_CS12 = [ 4, 5, 6 ];

int[] allItems = [ ..numbers1_CS12, ..numbers2_CS12 ];

int[] allItems_CS11 = numbers1_CS12.Concat(numbers2_CS12).ToArray();

int[] join = [..a, ..b, ..c, 6, 5];

int[] a =[1, 2, 3];
Span<int> b = [2, 4, 5, 4, 4];
List<int> c = [4, 6, 6, 5];

List<int> join = [..a, ..b, ..c, 6, 5];

List<(string, int)> otherScores = [("Dave", 90), ("Bob", 80)];

(string name, int score)[] scores = [("Alice", 90), ..otherScores, ("Charlie", 70)];

.NET 5 Preview 7 is now available and is ready for evaluation. Here’s what’s new in this release:

• Blazor WebAssembly apps now target .NET 5
• Updated debugging requirements for Blazor WebAssembly
• Blazor accessibility improvements
• Blazor performance improvements
• Certificate authentication performance improvements
• Sending HTTP/2 PING frames
• Support for additional endpoints types in the Kestrel sockets transport
• Custom header decoding in Kestrel
• Other minor improvements