Skip to content
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 6 [WIP] #6325

Closed
leecow opened this issue Jun 3, 2021 · 6 comments
Closed

What's new in .NET 6 Preview 6 [WIP] #6325

leecow opened this issue Jun 3, 2021 · 6 comments

Comments

@leecow
Copy link
Member

leecow commented Jun 3, 2021

What's new in .NET 6 Preview 6

This issue is for teams to highlight work for the community that will release .NET 6 Preview 6.

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.

## Team Name: Feature title

[link to the tracking issue or epic item for the work]

Tell the story of the feature and anything the community should pay particular attention 
to be successful using the feature.

Preview 1: #5853
Preview 2: #5889
Preview 3: #5890
Preview 4: #6098
Preview 5: #6099
Preview 7: #6444

@joperezr
Copy link
Member

joperezr commented Jun 4, 2021

Added TLS support for System.DirectoryServices.Protocols in Unix, which was one of the biggest gaps between the Windows and new Unix implementation. PR: dotnet/runtime#52904

Provided by community member @iinuwa

@mangod9
Copy link
Member

mangod9 commented Jun 28, 2021

crossgen2 is the only option for PublishReadyToRun starting preview6

As we continue the journey of enabling crossgen2, we have now removed crossgen from the Microsoft.NETCore.App package. As part of this change the SDK doesnt support using crossgen for PublishReadyToRun. You still have the ability to choose composite or non-composite.

      <PublishReadyToRun>true</PublishReadyToRun> 
      <PublishReadyToRunComposite>false</PublishReadyToRunComposite> <!-- swtich to true to generate a composite R2R image -->
      <PublishReadyToRunUseCrossgen2>true</PublishReadyToRunUseCrossgen2> <!-- This is a NOP -->

@JulieLeeMSFT
Copy link
Member

JulieLeeMSFT commented Jun 29, 2021

CodeGen

Dynamic PGO dotnet/runtime#43618

(Modified LSRA content in #6325 (comment))
### LSRA dotnet/runtime#43318
- Refactor LSRA's heuristics selection dotnet/runtime#52832
-- Now, DEBUG mode includes a COMPlus variable that LsraOrdering will let the user set the heuristics ordering.

W^X

@kouvel
Copy link
Member

kouvel commented Jun 30, 2021

Threading

Improved the rate of thread injection for blocking due to sync-over-async (dotnet/runtime#53471)

  • Sync-over-async is a common type of blocking work. When it happens on thread pool worker threads it can lead to starvation, and the slow thread injection may delay other queued work from running, also delaying the starvation from being resolved.
  • This change improved the rate of thread injection by default when sync-over-async is the only type of blocking work happening on thread pool worker threads. There are some new AppContext config values that can be used to configure the rate of thread injection in response to sync-over-async.

@JulieLeeMSFT
Copy link
Member

JulieLeeMSFT commented Jul 8, 2021

CodeGen

LSRA

image
image
image

More details: windows x86 improvements, windows x64 improvements and here.

Code quality

@marcpopMSFT
Copy link
Member

marcpopMSFT commented Jul 8, 2021

.NET SDK Optional Workload improvements

Building on the work that released in preview 4 for optional workloads and the new features of list and update that we added for preview 5, we have added three new commands for preview 6
dotnet workload search will show the list of workloads available to install
dotnet workload repair will re-install all workloads you've previously installed. This is useful if your install fails in the middle because of a dropped internet connection. Optional workloads are made up of multiple workload packs and you may have gotten into a state where some installed successfully but others didn't.
dotnet workload uninstall will remove the specified workload from your system to free up space if you no longer require a workload.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants