Today, we released the July 2018 Update that fixes an issue in .NET Framework 2.0, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2. We recommend that you apply this update if you are experiencing the issue described in the known issues Knowledge Base article 4345913 and the Blog Advisory.
Accounting for this change on Windows build servers: You may be doing one of the following things to install F# on a Windows build server. Installing the full Visual Studio IDE Installing the F# Compiler SDK MSI Neither of these options have been recommended for some time, but are still available with F# 4.1. For using F# 4.5 in a Windows build server, we recommend (in order of preference), Using the .NET SDK, the FSharp.Compiler.Tools package, or the Visual Studio Build Tools SKU.
Better async stack traces Starting with F# 4.5 and FSharp.Core 4.5.0, stack traces for async computation expressions: Reported line numbers now correspond to the failing user code Non-user code is no longer emitted For example, consider the following DSL and its usage with an FSharp.Core version prior to 4.5.0: Note that both the f1 and f2 functions are called twice.
Update as of 7/30/2018:
A new .NET Framework July 2018 Update has been released that resolves this advisory. We recommend that you install this update on your systems if you experienced the symptoms described in this advisory. If you did not experience these symptoms,
We released the first Early Access build for the .NET Framework 4.8 last month (June-2018) and are happy to announce the next build (3632) for your feedback. This is one of the in-development builds of the next version of the .NET Framework and includes incremental fixes from the last build (3621).
We are currently working on the IL Linker and would love to get your feedback. Please fill out the brief survey below and help shape the future of the IL Linker by telling us about your current practices as well as your biggest challenges with the build and deployment processes for your apps.
8/20/2019 Update: The .NET 4.7.2 update has been republished to work around a known issue in Config Manager that resulted in errors when Config Manager tried to sync with an upstream WSUS server. Please note that there is no change to the installers below.
Today, we are releasing the .NET Core July 2018 Update. This update includes .NET Core 1.0.12, .NET Core 1.1.9, .NET Core 2.0.9 and .NET Core 2.1.2.
.NET Core Security Feature Bypass Vulnerability
Microsoft is aware of a security feature bypass vulnerability that exists when .NET Core does not correctly validate certificates.
Two months ago, at //Build 2018, we released ML.NET 0.1, a cross-platform, open source machine learning framework for .NET developers. We’ve gotten great feedback so far and would like to thank the community for your engagement as we continue to develop ML.NET together in the open.
System.IO.Pipelines is a new library that is designed to make it easier to do high performance IO in .NET. It’s a library targeting .NET Standard that works on all .NET implementations.
Pipelines was born from the work the .NET Core team did to make Kestrel one of the fastest web servers in the industry.