-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What's new in .NET 6 Preview 1 #5853
Comments
.NET Libraries: System.Numerics - New math APIsNew math APIs which may be hardware accelerated if the underlying hardware supports it:
New math API overloads:
|
.NET Libraries: System.Threading.AccessControl - Ported Windows ACL APIsNew overloads were added to the These APIs are Windows-specific and available via the namespace System.Threading
{
public static partial class EventWaitHandleAcl
{
public static EventWaitHandle OpenExisting(string name, EventWaitHandleRights rights);
public static bool TryOpenExisting(string name, EventWaitHandleRights rights, out EventWaitHandle result);
}
public static partial class MutexAcl
{
public static Mutex OpenExisting(string name, MutexRights rights);
public static bool TryOpenExisting(string name, MutexRights rights, out Mutex result);
}
public static partial class SemaphoreAcl
{
public static Semaphore OpenExisting(string name, SemaphoreRights rights);
public static bool TryOpenExisting(string name, SemaphoreRights rights, out Semaphore result);
}
} |
AppModel"Superhost" for Windows and Mac: dotnet/runtime#43072In 5.0 we debuted the "superhost" for Linux, which linked all the CoreCLR native binaries into a single host, and embedded all libraries inside the same file, avoiding any file extraction. In 6.0 we're continuing this work by brining the superhost to Windows and Mac, meaning users can now publish a single-file binary that has exactly one file on disk and does not need to extract any of the core runtime assemblies to temporary directories. Facilitate single-file signing on MacOS: dotnet/runtime#3671Signing/notarization on MacOS has very strict requirements for the layout of binaries. This change fixes single-file to conform to those requirements, allowing single-file apps to be notarized and signed. |
.NET CoreCLR Runtime: Support Apple Silicon dotnet/runtime#43313.NET Rosetta 2 Emulation dotnet/runtime#44897Apple release of Big Sur 11.2 Beta 2 has resolved most issue running .NET 5.0 under Rosetta 2 emulation. Prior to Big Sur 11.2 Beta 2 there were significant issues with Rosetta 2 emulation, upgrade of
.NET 6 - CoreCLR Native dotnet/runtime#43313Native support for Apple Silicon is mostly complete in .NET 6.0 Preview 1. Native arm64 packages are now available Known issues:
Workarounds: To work around the lack of debugger support, it is recommended to either:
|
SDK: .NET CLI adopting the System.CommandLine librariesAdopting System.CommandLine lights up three features in the .NET CLI
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Portable Threadpool is enabled by default.This is a managed implementation of the runtime Threadpool. More details are included as part of this PR: dotnet/runtime#38225. We dont expect any functional or performance impact as part of this change, but if there is any issue it can be disabled using |
System.Private.Corelib assembly now precompiled by crossgen2We have started to roll broader crossgen2 based pre-compilation. In preview1 corelib is compiled using crossgen2. Going forward we expect all Framework assemblies would be compiled with it. We havent observed any performance differences, but there are a few differences with crossgen1 in terms of which methods are compiled. The sdk still defaults to using crossgen1 however and that will be moved over in subsequent .net 6 previews. |
.NET 6 Preview 1 was released: https://devblogs.microsoft.com/dotnet/announcing-net-6-preview-1/ |
What's new in .NET 6 Preview 1
This issue is for teams to highlight work for the community that will release .NET 6 Preview 1.
To add content, use a new conversation entry. The entry should include the team name and feature title as the first line as shown in the template below.
Preview 1: #5853
Preview 2: #5889
Preview 3: #5890
Preview 4: #6098
Preview 5: #6099
Preview 6: #6325
Preview 7: #6444
RC1: #6569
RC2: #6570
The text was updated successfully, but these errors were encountered: