Free. Cross-platform. Open source. A developer platform for building all your apps.
Today, we are releasing the December 2019 Security and Quality Rollup Updates for .NET Framework.
Quality and Reliability
This release contains the following quality and reliability improvements.
ASP.NET
ASP.NET will now emit a SameSite cookie header when HttpCookie.SameSite value is “None”
Over the past year, we’ve been working with the Windows Server team to make Windows Server Core container images a lot smaller. They are now 40% smaller! The Windows Server team has already published the new images in the Server Core Insider Docker repo,
We open sourced our new GC Perf Infrastructure! It’s now part of the dotnet performance repo. I’ve been meaning to write about it ‘cause some curious minds had been asking when they could use it after I blogged about it last time but didn’t get around to it till now.
.NET Core 2.2 was released on December 4, 2018. As a non-LTS (“Current”) release, it is supported for three months after the next release. .NET Core 3.0 was released on September 23, 2019. As a result, .NET Core 2.2 is supported until December 23,
We are happy to announce the new preview version of the .NET Core Windows Forms designer, which is available with the Visual Studio 16.5 Preview 1.
The big news is that the designer is now part of Visual Studio! This means that installing the .NET Core Windows Forms designer from a separate VSIX is no longer needed!
Announcing Entity Framework Core 3.1 and Entity Framework 6.4
We are excited to announce the general availability of EF Core 3.1 and EF 6.4 on nuget.org.
The final versions of .NET Core 3.1 and ASP.NET Core 3.1 are also available now.
Announcing .NET Core 3.1
We’re excited to announce the release of .NET Core 3.1. It’s really just a small set of fixes and refinements over .NET Core 3.0, which we released just over two months ago. The most important feature is that .NET Core 3.1 is an long-term supported (LTS) release and will be supported for three years.
Probably the most impactful feature of C# 8.0 is Nullable Reference Types (NRTs). It lets you make the flow of nulls explicit in your code, and warns you when you don’t act according to intent.
The NRT feature holds you to a higher standard on how you deal with nulls,
Today, we are releasing the November 2019 Preview of Quality Rollup
Quality and Reliability
This release contains the following quality and reliability improvements for .NET Framework for Windows 8.1, Server 2012 R2, Server 2012, Windows 7 SP1, Server 2008 R2 SP1 and Server 2008 SP2.
Today, we are releasing the .NET Core November 2019 Update. These updates only contain non-security fixes. See the individual release notes for details on updated packages.
NOTE: If you are a Visual Studio user, there are MSBuild version requirements so use only the .NET Core SDK supported for each Visual Studio version.
AI Machine Learning
Coinciding with the Microsoft Ignite 2019 conference, we are thrilled to announce the GA release of ML.NET 1.4 and updates to Model Builder in Visual Studio, with exciting new machine learning features that will allow you to innovate your .NET applications.
We are excited today to announce updates to Model Builder and improvements in ML.NET. You can learn more in the “What’s new in ML.NET?.” session at .NET Conf.
ML.NET is an open-source and cross-platform machine learning framework (Windows, Linux, macOS) for .NET developers.
ML.NET is an open source and cross-platform machine learning framework made for .NET developers.
Using ML.NET you can easily build custom machine learning models for scenarios like sentiment analysis, price prediction, sales forecasting, recommendation, image classification, and more.
ML.NET 1.0 was released at //Build 2019,
We are excited to announce ML.NET 1.2 and updates to Model Builder and the CLI. ML.NET is an open-source and cross-platform machine learning framework for .NET developers. ML.NET also includes Model Builder (a simple UI tool for Visual Studio) and the ML.NET CLI (Command-line interface) to make it super easy to build custom Machine Learning (ML) models using Automated Machine Learning (AutoML).
This post was written by Lena Hall, a Senior Cloud Developer Advocate at Microsoft.
F# Software Foundation has recently announced their new initiative — Applied F# Challenge! We encourage you to participate and send your submissions about F# on Azure through the participation form.
![Bri Achtman [MSFT]](https://web.archive.org/web/20191211092422/https://devblogs.microsoft.com/dotnet/wp-content/uploads/sites/10/2019/02/BriAchtman.jpeg){kind=avatar}
ML.NET is an open source and cross-platform machine learning framework made for .NET developers. .NET developers can use their C# or F# skills to easily integrate custom machine learning into their web, mobile, desktop, gaming, or IoT applications without any prior expertise in developing or tuning machine learning models.
ML.NET is an open-source and cross-platform framework (Windows, Linux, macOS) which makes machine learning accessible for .NET developers.
ML.NET allows you to create and use machine learning models targeting scenarios to achieve common tasks such as sentiment analysis, issue classification, forecasting,
We’re excited to announce today the release of ML.NET 0.7 – the latest release of the cross-platform and open source machine learning framework for .NET developers (ML.NET 0.1 was released at //Build 2018). This release focuses on enabling better support for recommendation based ML tasks,
This week’s blog post is by Brian Lui, one of our summer interns on the .NET team, who’s been hard at work. Over to Brian:
Hello everyone! This summer I interned in the .NET team, working on ML.NET, an open-source machine learning platform which enables .NET developers to build and use machine learning models in their .NET applications.
Today we’re announcing our latest monthly release: ML.NET 0.6! ML.NET is a cross-platform, open source machine learning framework for .NET developers. We want to enable every .NET developer to train and use machine learning models in their applications and services. If you haven’t tried ML.NET yet,
ASP.NET
Today, we are releasing the .NET Core April 2019 Update. These updates contain security and reliability fixes. See the individual release notes for details on included fixes.
.NET Core 2.2.4 and .NET Core SDK 2.2.106 ( Download | Release Notes )
.NET Core 2.1.10 and .NET Core SDK 2.1.506 ( Download | Release Notes)
Security
Microsoft Security Advisory CVE-2019-0815: ASP.NET Core Denial of Service Vulnerability
A denial of service vulnerability exists in ASP.NET Core 2.2 where,
It is challenging to collect performance traces of ASP.NET Core applications running inside Linux containers. This blog post describes an approach that use a sidecar container to collect CPU trace of an ASP.NET application running in a Linux container.
Connecting to databases and services is an important part of desktop application development for many of our customers. Visual Studio provides a variety of tools and technologies that can help you connect to and interact with your different data sources. We’d love your help in shaping our future offerings in this space!
Earlier this year, I wrote about an update to the roadmap for F# and .NET Core. I had mentioned that there were a number of things you could build with F# and .NET Core today, such as web services. In this post,
Get Started with F# as a C# developer
One of our previous posts, Why You Should Use F#, listed a few reasons why F# is worth trying out today. In this post, we’ll cover some of the basics you need to know to be successful.
Azure
We can all agree that tracking the progress of a project enhances productivity and is an effective way to keep everyone involved of its progress. When it comes to managing your project in Azure DevOps (formerly VSTS) or GitHub, you have all of your artifacts in one place: code,
C#
You can now write .NET Code in Jupyter Notebooks. Try .NET has grown to support more interactive experiences across the web with runnable code snippets, interactive documentation generator for .NET core with dotnet try global tool, and now .NET in Jupyter Notebooks. And you can get started with it today!
We are excited to announce ML.NET 1.4 Preview and updates to Model Builder and CLI.
ML.NET is an open-source and cross-platform machine learning framework for .NET developers. ML.NET also includes Model Builder (a simple UI tool) and CLI to make it super easy to build custom Machine Learning (ML) models using Automated Machine Learning (AutoML).
Try .NET is an interactive documentation generator for .NET Core. Using the dotnet try global tool you can now create interactive documentation too. This is an early preview of the dotnet try global tool so, please check our repository and NuGet package for regular updates.
Take a tour through some of the many improvements, big and small, that have gone into the .NET Core 3.0 runtime and core libraries to make apps and services leaner and faster.
Default implementations in interfaces
With last week’s posts Announcing .NET Core 3.0 Preview 5 and Visual Studio 2019 version 16.1 Preview 3, the last major feature of C# 8.0 is now available in preview.
A big impediment to software evolution has been the fact that you couldn’t add new members to a public interface.
Today, we are announcing .NET Core 3.0 Preview 5. It includes a new Json serializer, support for publishing single file executables, an update to runtime roll-forward, and changes in the BCL. If you missed it, check out the improvements we released in .NET Core 3.0 Preview 4,
Your friendly neighborhood .NET productivity team (aka. Roslyn) focuses a lot on improving the .NET coding experience. Sometimes it’s the little refactorings and code fixes that really improve your workflow. You may have seen many improvements in the previews, but for all of you who were eagerly awaiting the GA release here’s a few features you may enjoy!
Starting with Visual Studio 2019 Preview 4, we'll be adjusting how C# versions are treated in .NET tooling. Firstly, we're adding two new Language Version (LangVersion) values: LatestMajor and Preview. Rad the post to see how they stack up with the currently supported list of values.
Take C# 8.0 for a spin
Yesterday we announced the first preview of both Visual Studio 2019 (Making every developer more productive with Visual Studio 2019) and .NET Core 3.0 (Announcing .NET Core 3 Preview 1 and Open Sourcing Windows Desktop Frameworks).
Building C# 8.0
The next major version of C# is C# 8.0. It’s been in the works for quite some time, even as we built and shipped the minor releases C# 7.1, 7.2 and 7.3, and I’m quite excited about the new capabilities it will bring.
Docker
Over the past year, we’ve been working with the Windows Server team to make Windows Server Core container images a lot smaller. They are now 40% smaller! The Windows Server team has already published the new images in the Server Core Insider Docker repo,
Today, we are announcing .NET Core 3.0 Preview 5. It includes a new Json serializer, support for publishing single file executables, an update to runtime roll-forward, and changes in the BCL. If you missed it, check out the improvements we released in .NET Core 3.0 Preview 4,
DockerCon 2019 is being held this week, in San Francisco. We posted a DockerCon 2018 update last year, and it is time to share how we’ve improved the experience of using .NET and Docker together over the last year.
We have a group of .NET Core team members attending the conference again this year.
Dot.Net
We open sourced our new GC Perf Infrastructure! It’s now part of the dotnet performance repo. I’ve been meaning to write about it ‘cause some curious minds had been asking when they could use it after I blogged about it last time but didn’t get around to it till now.
Today, we’re announcing .NET Core 3.0 Release Candidate 1. Just like with Preview 9, we’ve focused on polishing .NET Core 3.0 for a final release. We are now getting very, very close. We intend to release the final version on September 23 at .NET Conf.
Years ago I wrote a document on making finalization scanning concurrent. At the time there was an internal team that was using finalization as a way to resurrect objects and putting them back in their cache. While we’ve always advised to folks that finalization was for releasing native resources I couldn’t fault this team for using it the way they did.
Today, we are releasing the .NET Core September 2019 Update. These updates contain security and reliability fixes. See the individual release notes for details on updated packages.
NOTE: If you are a Visual Studio user, there are MSBuild version requirements so use only the .NET Core SDK supported for each Visual Studio version.
Today, we’re announcing .NET Core 3.0 Preview 9. Just like with Preview 8, we’ve focused on polishing .NET Core 3.0 for a final release and aren’t adding new features. If these final builds seem less exciting than earlier previews, that’s by design.
.NET Conf is back again this year and will be live streaming to a device near you September 23-25 on www.dotnetconf.net! .NET Conf is a FREE, 3 day virtual developer event co-organized by the .NET community and Microsoft. This year .NET Core 3.0 will launch at .NET Conf 2019!
Producing Docker images for .NET might not seem like that big of a deal. Once you’ve got a Dockerfile defined, just run “docker build“ and “docker push“ and you’re done, right? Then just rinse and repeat when new versions of .NET are released and that should be all that’s needed.
The .NET team is constantly thinking of new ways to make developers more productive. We’ve been working hard over the past year to take the feedback you’ve sent us and turn it into tools that you want! In this post I’ll cover some of the latest productivity features available in Visual Studio 2019 Preview.
We are happy to announce that Microsoft .NET Framework 4.8 is now available on Windows Update, Windows Server Update Services (WSUS) and Microsoft Update (MU) Catalog. This release includes quality and reliability fixes based on feedback since the .NET Framework 4.8 initial release.
Today, we are announcing .NET Core 3.0 Preview 8. Just like with Preview 7, we’ve focused on polishing .NET Core 3.0 for a final release and are not adding new features. If these final previews seem anti-climatic, that’s by design.
Download .NET Core 3.0 Preview 8 right now on Windows,
Entity Framework
Announcing Entity Framework Core 3.1 and Entity Framework 6.4
We are excited to announce the general availability of EF Core 3.1 and EF 6.4 on nuget.org.
The final versions of .NET Core 3.1 and ASP.NET Core 3.1 are also available now.
We are extremely excited to announce the general availability of EF Core 3.0and EF 6.3 on nuget.org.
The final versions of .NET Core 3.0 and ASP.NET Core 3.0 are also available now.
How to get EF Core 3.0
EF Core 3.0 is distributed exclusively as a set of NuGet packages.
We previously said that preview 9 would be your last chance to test EF Core 3.0 and EF 6.3 before general availability. But it turns out that we made enough improvements to our libraries and across the whole of .NET Core 3.0 to justify publishing a release candidate build.
Preview 9 your last chance to try Entity Framework Core 3.0 and Entity Framework 6.3 before we release the final versions later this month. Get a head start on everything that is new and please give us your feedback.
The Preview 8 versions of the EF Core 3.0 package and the EF 6.3 package are now available for download from nuget.org.
New previews of .NET Core 3.0 and ASP.NET Core 3.0 are also available today.
Please install these previews to validate that all the functionality required by your applications is available and works correctly.
New previews of the next versions of EF Core and EF 6 are now available on NuGet.Org.
What is new in EF Core 3.0 Preview 6
In recent months, a lot of our efforts have been focused on a new LINQ implementation for EF Core 3.0.
The first preview of the EF 6.3 runtime is now available in NuGet.
Note that the package is versioned as 6.3.0-preview5. We plan to continue releasing previews of EF 6.3 every month in alignment with the .NET Core 3.0 previews, until we ship the final version.
Today, we are making the fourth preview of Entity Framework Core 3.0 available on NuGet, alongside .NET Core 3.0 Preview 4 and ASP.NET Core 3.0 Preview 4. We encourage you to install this preview to test the new functionality and assess the impact of the included breaking changes.
Today we’re making the final version of EF Core 2.2 available, alongside ASP.NET Core 2.2 and .NET Core 2.2. This is the latest release of our open-source and cross-platform object-database mapping technology.
EF Core 2.2 RTM includes more than a hundred bug fixes and a few new features:
Spatial data support
Spatial data can be used to represent the physical location and shape of objects.
Entity Framework Core 2.2 Preview 3 available with a new preview of our data provider for Cosmos DB and updated spatial extensions for various providers. Preview 3 is going to be the last milestone before EF Core 2.2 RTM, so now is your last chance to try the bits and give us feedback if you want to have an impact on the quality and the shape of the APIs in this release.
F#
You can now write .NET Code in Jupyter Notebooks. Try .NET has grown to support more interactive experiences across the web with runnable code snippets, interactive documentation generator for .NET core with dotnet try global tool, and now .NET in Jupyter Notebooks. And you can get started with it today!
TL;DR We’ve moved the F# GitHub repository from microsoft/visualfsharp to dotnet/fsharp, as specified in the corresponding RFC.
F# has a somewhat strange history in its name and brand. If we roll back the clocks to the year 2015, F# sort of had two identities.
We’re excited to announce general availability of F# 4.6 and the F# tools for Visual Studio 2019! In this post, I’ll show you how to get started, explain the F# 4.6 feature set, give you an update on the F# tools for Visual Studio,
This post was written by Lena Hall, a Senior Cloud Developer Advocate at Microsoft.
F# Software Foundation has recently announced their new initiative — Applied F# Challenge! We encourage you to participate and send your submissions about F# on Azure through the participation form.
F# 4.6 is now fully released. See the announcement blog post for more.
We’re excited to announce that Visual Studio 2019 will ship a new version of F# when it releases: F# 4.6!
F# 4.6 is a smaller update to the F# language,
Today, we’re incredibly pleased to announce general availability of F# 4.5.
This post will walk through the changes in F# 4.5 (just like the preview post), then show some updates to F# tooling, and finally talk a bit about where what we’re thinking about for the next F# version.
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.
We’re excited to share updates about changes to F# and F# tools which shipped with the Visual Studio 2017 version 15.7 release. Let’s dive in!
Type Providers now support .NET Standard
For those who aren’t familiar with Type Providers, they are a feature of F# which allow you to get IntelliSense for data.
With the release of Visual Studio 2017 version 15.6, we’re excited to share updates to the F# language and core library, F# tooling in Visual Studio, and infrastructure updates that concern OSS contributors. Let’s dive in!
F# language and core library updates
Some foundational changes for the F# language and core library have been made,
We’re pleased to announce that Visual Studio 2017 15.5 Preview 4 now supports F# projects targeting .NET Core, .NET Standard, and .NET Framework through the .NET Core SDK. Some of you have noticed various levels of this support in the first,
GC
In this blog entry and some future ones I will be showing off functionalities that our new GC perf infrastructure provides. Andy and I have been working on it (he did all the work; I merely played the consultant role). We will be open sourcing it soon and I wanted to give you some examples of using it and you can add these to your repertoire of perf analysis techniques when it’s available.
LOH
I wrote this article in 2008 and the MSDN website no longer has it so I am making it available here. Please note that it has been quite a while and some things related to LOH have changed quite a bit.
Machine Learning
Coinciding with the Microsoft Ignite 2019 conference, we are thrilled to announce the GA release of ML.NET 1.4 and updates to Model Builder in Visual Studio, with exciting new machine learning features that will allow you to innovate your .NET applications.
We are excited today to announce updates to Model Builder and improvements in ML.NET. You can learn more in the “What’s new in ML.NET?.” session at .NET Conf.
ML.NET is an open-source and cross-platform machine learning framework (Windows, Linux, macOS) for .NET developers.
We are excited to announce ML.NET 1.4 Preview and updates to Model Builder and CLI.
ML.NET is an open-source and cross-platform machine learning framework for .NET developers. ML.NET also includes Model Builder (a simple UI tool) and CLI to make it super easy to build custom Machine Learning (ML) models using Automated Machine Learning (AutoML).
ML.NET is an open source and cross-platform machine learning framework made for .NET developers.
Using ML.NET you can easily build custom machine learning models for scenarios like sentiment analysis, price prediction, sales forecasting, recommendation, image classification, and more.
ML.NET 1.0 was released at //Build 2019,
We’re excited to announce general availability of F# 4.6 and the F# tools for Visual Studio 2019! In this post, I’ll show you how to get started, explain the F# 4.6 feature set, give you an update on the F# tools for Visual Studio,
This post was written by Lena Hall, a Senior Cloud Developer Advocate at Microsoft.
F# Software Foundation has recently announced their new initiative — Applied F# Challenge! We encourage you to participate and send your submissions about F# on Azure through the participation form.
Announcing ML.NET 0.9 – Machine Learning for .NET
ML.NET is an open-source and cross-platform machine learning framework (Windows, Linux, macOS) for .NET developers. Using ML.NET, developers can leverage their existing tools and skillsets to develop and infuse custom AI into their applications by creating custom machine learning models.
Today we’re announcing our latest monthly release: ML.NET 0.6! ML.NET is a cross-platform, open source machine learning framework for .NET developers. We want to enable every .NET developer to train and use machine learning models in their applications and services. If you haven’t tried ML.NET yet,
Why you should use F#
This post was written by Phillip Carter and Mads Torgersen. Both work on languages on the .NET team.
At Build 2017, we presented a tech talk entitled “Why You Should Use F#”. However, not everyone can attend Build,
Maoni
We open sourced our new GC Perf Infrastructure! It’s now part of the dotnet performance repo. I’ve been meaning to write about it ‘cause some curious minds had been asking when they could use it after I blogged about it last time but didn’t get around to it till now.
In this blog entry and some future ones I will be showing off functionalities that our new GC perf infrastructure provides. Andy and I have been working on it (he did all the work; I merely played the consultant role). We will be open sourcing it soon and I wanted to give you some examples of using it and you can add these to your repertoire of perf analysis techniques when it’s available.
ML.NET
ML.NET is a cross-platform, machine learning framework for .NET developers, and Model Builder is the UI tooling in Visual Studio that uses Automated Machine Learning (AutoML) to easily allow you to train and consume custom ML.NET models.
Coinciding with the Microsoft Ignite 2019 conference, we are thrilled to announce the GA release of ML.NET 1.4 and updates to Model Builder in Visual Studio, with exciting new machine learning features that will allow you to innovate your .NET applications.
We are excited today to announce updates to Model Builder and improvements in ML.NET. You can learn more in the “What’s new in ML.NET?.” session at .NET Conf.
ML.NET is an open-source and cross-platform machine learning framework (Windows, Linux, macOS) for .NET developers.
We are excited to announce ML.NET 1.4 Preview and updates to Model Builder and CLI.
ML.NET is an open-source and cross-platform machine learning framework for .NET developers. ML.NET also includes Model Builder (a simple UI tool) and CLI to make it super easy to build custom Machine Learning (ML) models using Automated Machine Learning (AutoML).
ML.NET is an open source and cross-platform machine learning framework made for .NET developers.
Using ML.NET you can easily build custom machine learning models for scenarios like sentiment analysis, price prediction, sales forecasting, recommendation, image classification, and more.
ML.NET 1.0 was released at //Build 2019,
We are excited to announce ML.NET 1.2 and updates to Model Builder and the CLI. ML.NET is an open-source and cross-platform machine learning framework for .NET developers. ML.NET also includes Model Builder (a simple UI tool for Visual Studio) and the ML.NET CLI (Command-line interface) to make it super easy to build custom Machine Learning (ML) models using Automated Machine Learning (AutoML).
ML.NET is an open-source and cross-platform machine learning framework (Windows, Linux, macOS) for .NET developers.
ML.NET offers Model Builder Model Builder (a simple UI tool for Visual Studio) and CLI to make it super easy to build custom ML Models using AutoML.
This post was written by Lena Hall, a Senior Cloud Developer Advocate at Microsoft.
F# Software Foundation has recently announced their new initiative — Applied F# Challenge! We encourage you to participate and send your submissions about F# on Azure through the participation form.
Announcing ML.NET 0.9 – Machine Learning for .NET
ML.NET is an open-source and cross-platform machine learning framework (Windows, Linux, macOS) for .NET developers. Using ML.NET, developers can leverage their existing tools and skillsets to develop and infuse custom AI into their applications by creating custom machine learning models.
We’re excited to announce today the release of ML.NET 0.7 – the latest release of the cross-platform and open source machine learning framework for .NET developers (ML.NET 0.1 was released at //Build 2018). This release focuses on enabling better support for recommendation based ML tasks,
.NET
Today, we are releasing the December 2019 Security and Quality Rollup Updates for .NET Framework.
Quality and Reliability
This release contains the following quality and reliability improvements.
ASP.NET
ASP.NET will now emit a SameSite cookie header when HttpCookie.SameSite value is “None”
Over the past year, we’ve been working with the Windows Server team to make Windows Server Core container images a lot smaller. They are now 40% smaller! The Windows Server team has already published the new images in the Server Core Insider Docker repo,
We open sourced our new GC Perf Infrastructure! It’s now part of the dotnet performance repo. I’ve been meaning to write about it ‘cause some curious minds had been asking when they could use it after I blogged about it last time but didn’t get around to it till now.
We are happy to announce the new preview version of the .NET Core Windows Forms designer, which is available with the Visual Studio 16.5 Preview 1.
The big news is that the designer is now part of Visual Studio! This means that installing the .NET Core Windows Forms designer from a separate VSIX is no longer needed!
Announcing .NET Core 3.1
We’re excited to announce the release of .NET Core 3.1. It’s really just a small set of fixes and refinements over .NET Core 3.0, which we released just over two months ago. The most important feature is that .NET Core 3.1 is an long-term supported (LTS) release and will be supported for three years.
Probably the most impactful feature of C# 8.0 is Nullable Reference Types (NRTs). It lets you make the flow of nulls explicit in your code, and warns you when you don’t act according to intent.
The NRT feature holds you to a higher standard on how you deal with nulls,
Today, we are releasing the November 2019 Preview of Quality Rollup
Quality and Reliability
This release contains the following quality and reliability improvements for .NET Framework for Windows 8.1, Server 2012 R2, Server 2012, Windows 7 SP1, Server 2008 R2 SP1 and Server 2008 SP2.
Today, we are releasing the .NET Core November 2019 Update. These updates only contain non-security fixes. See the individual release notes for details on updated packages.
NOTE: If you are a Visual Studio user, there are MSBuild version requirements so use only the .NET Core SDK supported for each Visual Studio version.
Today, we’re announcing .NET Core 3.1 Preview 3. .NET Core 3.1 is a small and short release focused on key improvements in Blazor and Windows desktop, the two big additions in .NET Core 3.0.. It will be a long term support (LTS) release.
Today, we released an update for .NET Framework 4.8 to Microsoft Update Catalog.
Quality and Reliability
This release contains the following reliability improvement.
CLR1
Addresses an issue where some ClickOnce applications or applications creating the default AppDomain with a restricted permission set may observe application launch or application runtime failures,
.NET Core
We open sourced our new GC Perf Infrastructure! It’s now part of the dotnet performance repo. I’ve been meaning to write about it ‘cause some curious minds had been asking when they could use it after I blogged about it last time but didn’t get around to it till now.
.NET Core 2.2 was released on December 4, 2018. As a non-LTS (“Current”) release, it is supported for three months after the next release. .NET Core 3.0 was released on September 23, 2019. As a result, .NET Core 2.2 is supported until December 23,
Today, we are releasing the .NET Core November 2019 Update. These updates only contain non-security fixes. See the individual release notes for details on updated packages.
NOTE: If you are a Visual Studio user, there are MSBuild version requirements so use only the .NET Core SDK supported for each Visual Studio version.
This is a guest post from the Pulumi team. Pulumi is an open source infrastructure as code tool that helps developers and infrastructure teams work better together to create, deploy, and manage cloud applications using their favorite languages. For more information,
Coinciding with the Microsoft Ignite 2019 conference, we are thrilled to announce the GA release of ML.NET 1.4 and updates to Model Builder in Visual Studio, with exciting new machine learning features that will allow you to innovate your .NET applications.
You can now write .NET Code in Jupyter Notebooks. Try .NET has grown to support more interactive experiences across the web with runnable code snippets, interactive documentation generator for .NET core with dotnet try global tool, and now .NET in Jupyter Notebooks. And you can get started with it today!
App Center is an integrated developer solution with the mission of helping developers build better apps. Last week, we announced General Availability support of distribute, analytics and diagnostics service for WPF and Windows Forms desktop applications. We also expanded our existing UWP offerings to include crash and error reporting for sideloaded UWP apps.
It’s been a busy time for .NET Core – we just shipped 3.0, and are currently working on a few updates for v3.1 (due in November.) As we turn our attention to .NET Core 5.0, we want to take a step back and see what you are doing with .NET Core and how we can make it even better.
We are excited today to announce updates to Model Builder and improvements in ML.NET. You can learn more in the “What’s new in ML.NET?.” session at .NET Conf.
ML.NET is an open-source and cross-platform machine learning framework (Windows, Linux, macOS) for .NET developers.
We are extremely excited to announce the general availability of EF Core 3.0and EF 6.3 on nuget.org.
The final versions of .NET Core 3.0 and ASP.NET Core 3.0 are also available now.
How to get EF Core 3.0
EF Core 3.0 is distributed exclusively as a set of NuGet packages.
.NET Framework
Over the past year, we’ve been working with the Windows Server team to make Windows Server Core container images a lot smaller. They are now 40% smaller! The Windows Server team has already published the new images in the Server Core Insider Docker repo,
We open sourced our new GC Perf Infrastructure! It’s now part of the dotnet performance repo. I’ve been meaning to write about it ‘cause some curious minds had been asking when they could use it after I blogged about it last time but didn’t get around to it till now.
Coinciding with the Microsoft Ignite 2019 conference, we are thrilled to announce the GA release of ML.NET 1.4 and updates to Model Builder in Visual Studio, with exciting new machine learning features that will allow you to innovate your .NET applications.
Today, we are releasing the October 2019 Security and Quality Rollup and Cumulative Updates for .NET Framework.
Security
No new security fixes. See September 2019 Security and Quality Rollup for the latest security updates.
Quality and Reliability
This release contains the following quality and reliability improvements.
Today, we are releasing the September 2019 Cumulative Update, Security and Quality Rollup, and Security Only Update for .NET Framework.
Security
CVE-2019-1142– .NET Framework Elevation of Privilege Vulnerability
An elevation of privilege vulnerability exists when the .NET Framework common language runtime (CLR) allows file creation in arbitrary locations.
The August 2019 Cumulative Update for .NET Framework 3.5 and 4.8 on Windows 10 version 1903 was released.
Quality and Reliability
This release contains the following quality and reliability improvements.
Addresses a crash that occurs after enumerating event logs.
Addresses a regression caused by the fix for the issue involving bindings with DataContext explicitly on the binding path.
Today, we are releasing the August 2019 Preview of Quality Rollup.
Quality and Reliability
This release contains the following quality and reliability improvements.
BCL1
Addresses a crash that occurs after enumerating event logs. [910822]
1 Base Class Library (BCL)
Getting the Update
The Preview of Quality Rollup is available via Windows Update,
We are excited to announce ML.NET 1.2 and updates to Model Builder and the CLI. ML.NET is an open-source and cross-platform machine learning framework for .NET developers. ML.NET also includes Model Builder (a simple UI tool for Visual Studio) and the ML.NET CLI (Command-line interface) to make it super easy to build custom Machine Learning (ML) models using Automated Machine Learning (AutoML).
Today, we are releasing the July 2019 Cumulative Update, Security and Quality Rollup, and Security Only Update for .NET Framework.
Security
CVE-2019-1006 – WCF/WIF SAML Token Authentication Bypass Vulnerability
An authentication bypass vulnerability exists in Windows Communication Foundation (WCF) and Windows Identity Foundation (WIF),
Today, we released the June 2019 Cumulative Update for .NET Framework 3.5 and 4.8 on Windows 10 version 1903.
Quality and Reliability
This release contains the following quality and reliability improvements.
Improves the memory allocation and cleanup scheduling behavior of the weak-event pattern.
Performance
We open sourced our new GC Perf Infrastructure! It’s now part of the dotnet performance repo. I’ve been meaning to write about it ‘cause some curious minds had been asking when they could use it after I blogged about it last time but didn’t get around to it till now.
In this blog entry and some future ones I will be showing off functionalities that our new GC perf infrastructure provides. Andy and I have been working on it (he did all the work; I merely played the consultant role). We will be open sourcing it soon and I wanted to give you some examples of using it and you can add these to your repertoire of perf analysis techniques when it’s available.
Several years ago, we decided that it was time to support SIMD code in .NET. We introduced the System.Numerics namespace with Vector2, Vector3, Vector4, Vector<T>, and related types. These types expose a general-purpose API for creating, accessing, and operating on them using hardware vector instructions (when available).
Take a tour through some of the many improvements, big and small, that have gone into the .NET Core 3.0 runtime and core libraries to make apps and services leaner and faster.
If you are running Windows on a machine with 64 CPUs, you’ll need to use this feature called the CPU groups for your process to be able to use more than 64 CPUs. At some point in the far distant past,
A customer who just experienced some server outage asked us for help as they thought it was due to some very long GC pauses. I thought this diagnostics exercise might be useful for other folks as well so I am sharing it with you.
A long time ago I wrote about using Workstation GC on server applications when you have many instances of your server app running on the same machine. By default Server GC will treat the process as owning the machine so it uses all CPUs to do the GC work.
End of last year I mentioned we wanted to provide an API for you to really investigate GC/managed memory related performance called GLAD. Well, the source finally got opened source on github. So GLAD is available. The repo is called PerfView but you actually just need the TraceEvent project (but it’s much easier to just build the whole solution then add the reference to the resulting Microsoft.Diagnostics.Tracing.TraceEvent.dll).
I wrote this article in 2008 and the MSDN website no longer has it so I am making it available here. Please note that it has been quite a while and some things related to LOH have changed quite a bit.
Security
Today, we are releasing the .NET Core July 2019 Update. These updates contain security and reliability fixes. See the individual release notes for details on updated packages.
NOTE: If you are a Visual Studio user, there are MSBuild version requirements so use only the .NET Core SDK supported for each Visual Studio version.
Today, we are releasing the .NET Core April 2019 Update. These updates contain security and reliability fixes. See the individual release notes for details on included fixes.
.NET Core 2.2.4 and .NET Core SDK 2.2.106 ( Download | Release Notes )
.NET Core 2.1.10 and .NET Core SDK 2.1.506 ( Download | Release Notes)
Security
Microsoft Security Advisory CVE-2019-0815: ASP.NET Core Denial of Service Vulnerability
A denial of service vulnerability exists in ASP.NET Core 2.2 where,
This post was written by Lena Hall, a Senior Cloud Developer Advocate at Microsoft.
F# Software Foundation has recently announced their new initiative — Applied F# Challenge! We encourage you to participate and send your submissions about F# on Azure through the participation form.
Today, we are releasing the January 2019 Security and Quality Rollup.
Security
CVE-2019-0545 – Windows Security Feature Bypass Vulnerability
This security update resolves a vulnerability in Microsoft .NET Framework that may cause an information disclosure that allows bypassing Cross-origin Resource Sharing (CORS) configurations.
Today, we are releasing the December 2018 Security and Quality Rollup.
Security
CVE-2018-8540 – Windows Remote Code Execution Vulnerability
This security update resolves a vulnerability in Microsoft .NET Framework that could allow remote code execution when Microsoft .NET Framework doesn’t validate input correctly.
Today, we are releasing the November 2018 Security and Quality Rollup.
Security
No new security fixes. See .NET Framework September 2018 Security and Quality Rollup for the latest security updates.
Quality and Reliability
This release contains the following quality and reliability improvements.
Today, we released the October 2018 Security and Quality Rollup.
Security
No new security fixes. See .NET Framework September 2018 Security and Quality Rollup for the latest security update.
Quality and Reliability
This release contains the following quality and reliability improvements.
Visual Studio
TL;DR We’ve moved the F# GitHub repository from microsoft/visualfsharp to dotnet/fsharp, as specified in the corresponding RFC.
F# has a somewhat strange history in its name and brand. If we roll back the clocks to the year 2015, F# sort of had two identities.
Your friendly neighborhood .NET productivity team (aka. Roslyn) focuses a lot on improving the .NET coding experience. Sometimes it’s the little refactorings and code fixes that really improve your workflow. You may have seen many improvements in the previews, but for all of you who were eagerly awaiting the GA release here’s a few features you may enjoy!
We’re excited to announce general availability of F# 4.6 and the F# tools for Visual Studio 2019! In this post, I’ll show you how to get started, explain the F# 4.6 feature set, give you an update on the F# tools for Visual Studio,
In the coming days, we’ll be moving our developer blogs to a new platform with a modern, clean design and powerful features that will make it easy for you to discover and share great content. This week, you’ll see the Visual Studio,
F# 4.6 is now fully released. See the announcement blog post for more.
We’re excited to announce that Visual Studio 2019 will ship a new version of F# when it releases: F# 4.6!
F# 4.6 is a smaller update to the F# language,
Another preview of Visual Studio 2019, another update on the cool stuff going into it!
We’re pleased to announce some updates to the .NET Core tools for Visual Studio 2019. You can try these changes out starting with Preview 2. We’d love for you to try out these new features and give us feedback.
Update! Starting with Visual Studio 2019, the option has moved to:
Tools Options Environment Preview Features
Old post for posterity:
Starting with Visual Studio 2017 version 15.9, we’ve changed how the Visual Studio tooling for .NET consumes .NET Core SDKs. Prior to this change,
Today, we’re incredibly pleased to announce general availability of F# 4.5.
This post will walk through the changes in F# 4.5 (just like the preview post), then show some updates to F# tooling, and finally talk a bit about where what we’re thinking about for the next F# version.
We’re excited to share updates about changes to F# and F# tools which shipped with the Visual Studio 2017 version 15.7 release. Let’s dive in!
Type Providers now support .NET Standard
For those who aren’t familiar with Type Providers, they are a feature of F# which allow you to get IntelliSense for data.
With the release of Visual Studio 2017 version 15.6, we’re excited to share updates to the F# language and core library, F# tooling in Visual Studio, and infrastructure updates that concern OSS contributors. Let’s dive in!
F# language and core library updates
Some foundational changes for the F# language and core library have been made,
WPF
App Center is an integrated developer solution with the mission of helping developers build better apps. Last week, we announced General Availability support of distribute, analytics and diagnostics service for WPF and Windows Forms desktop applications. We also expanded our existing UWP offerings to include crash and error reporting for sideloaded UWP apps.
In part 1 of this blog series, I began the process of porting a sample WPF app to .NET Core. In that post, I described the .NET Core migration process as having four steps:
We previously went through the first two steps –
Olia recently wrote a post about how to port a WinForms app from .NET Framework to .NET Core. Today, I’d like to follow that up by walking through the steps to migrate a sample WPF app to .NET Core 3. Many of these steps will be familiar from Olia’s post,
Since I’ve been working with the community on porting desktop applications from .NET Framework to .NET Core, I’ve noticed that there are two camps of folks: some want a very simple and short list of instructions to get their apps ported to .NET Core while others prefer a more principled approach with more background information.
Today, we are announcing .NET Core 3.0 Preview 4. It includes a chart control for Windows Forms, HTTP/2 support, GC updates to use less memory, support for CPU limits with Docker, the addition of PowerShell in .NET Core SDK Docker container images,
In this post, I will describe how to port a desktop application from .NET Framework to .NET Core. I picked a WinForms application as an example. Steps for WPF application are similar and I’ll describe what needs to be done different for WPF as we go.
Today, we are excited to announce that we are open sourcing XAML Behaviors for WPF.
In the past, we open sourced XAML Behaviors for UWP which has been a great success and the Behaviors NuGet package has been downloaded over 500k times.
Download Portability Analyzer (2.37 MB)
At Build 2018 we announced that we are enabling Windows desktop applications (Windows Forms and Windows Presentation Framework (WPF)) with .NET Core 3.0. You will be able to run new and existing Windows desktop applications on .NET Core and enjoy all the benefits that .NET Core has to offer,
This post describes the new WPF and accessibility features and improvements in .NET Framework 4.7.1. You can try out these features by downloading the Developer Pack, described in the Welcome to the .NET Framework 4.7.1 Early Access blog post.
Accessibility improvements
.NET Framework 4.7.1 brings in a lot of accessibility improvements across different libraries to align with the broad Microsoft product accessibility goals.
You can now install the July 2017 Quality Update for WPF. It applies to multiple Windows versions.
This update resolves known issue 4033488. It is recommended on machines that have installed the July 2017 Preview of Quality Rollup or the May 2017 Preview of Quality Rollup.
XAML
Today, we are excited to announce that we are open sourcing XAML Behaviors for WPF.
In the past, we open sourced XAML Behaviors for UWP which has been a great success and the Behaviors NuGet package has been downloaded over 500k times.