.NET Blog
Free. Cross-platform. Open source. A developer platform for building all your apps.
Latest posts
Announcing ML.NET 0.3
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. We are happy to announce the latest version: ML.NET 0.3. This release supports exporting models to the ONNX format, enables creating new types of models with Factorization Machines, LightGBM, Ensembles, and LightLDA, and addressing a variety of issues and feedback we received from the community. The main highlights of ML.NET 0.3 ...
System.IO.Pipelines: High performance IO in .NET
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. What started as an implementation detail inside of Kestrel progressed into a re-usable API that shipped in 2.1 as a first class BCL API (System.IO.Pipelines) available for all .NET developers. What problem does it solve? Correctly parsing data from a stream or socket is dominated by boilerplate code and has ...
Workaround for Bower Version Deprecation
As of June 25, the version of Bower shipped with Visual Studio was deprecated, resulting in Bower operations failing when run in Visual Studio. If you use Bower, you will see an error something like: This will be fixed in Visual Studio 15.8. In the meantime, you can work around the issue by using a new version of Bower or by adding some configuration to each Bower project. The Issue Some time, ago Bower switched their primary registry feed but continued to support both. On June 25th, they turned off the older feed, which the copy in Visual Studio tries to use by default. The Fix There are two options to fi...
NuGet Summer 2018 Roadmap
This blog post provides insights into the NuGet team plans for the upcoming quarter (July - Sep 2018). In the March 2018 NuGet Spring 2018 Roadmap, we had outlined Package Signing, Organizations, Cross-platform credential provider support, Repeatable builds for PackageReference based projects, etc. as our immediate priorities. We were able to complete much of this work over the past few months and have made good progress on others. In this blog post, I would like to summarize our progress and share our plans for the next quarter. Looking back Here is a quick summary of various experiences that we enabled over t...
Changes to script debugging in Visual Studio 15.7
We’re always looking for ways to make developing with Visual Studio faster. One of the tasks developers do many times a day is launching debugging sessions. We identified that script debugging added about 1.5s per F5, but only about 15.5% of people actively debugged script using Visual Studio. Based on the above, in Visual Studio 15.7 we made the decision to turn off script debugging by default to improve the overall experience for most users. If you want to turn the capability back on, you can do it from Tools | Options | Debugging | and check “Enable JavaScript debugging for ASP.NET (Chrome, Edge, and IE): ...
.NET Core 2.1 June Update
We released .NET Core 2.1.1. This update includes .NET Core SDK 2.1.301, ASP.NET Core 2.1.1 and .NET Core 2.1.1. See .NET Core 2.1.1 release notes for complete details on the release. Quality Updates CLI CoreCLR CoreFX WCF Getting the Update The .NET Core 2.1 June 2018 Update is available from the .NET Core 2.1.1 download page. You can always download the latest version of .NET Core at .NET Downloads. Docker Images .NET Docker images have been updated for today’s release. The following repos have been updated. Note: Look at the “Tags” v...
.NET Core 2.0 will reach End of Life on October 1, 2018
Last Updated: 6/22/2018 .NET Core 2.0 was released on August 14, 2017. As a non-LTS release, it is supported for 3 months after the next release. .NET Core 2.1 was released on May 30th, 2018. As a result, .NET Core 2.0 will be supported until September 1, 2018. NEW: Customers have reported a narrow but critical diagnostics issue with .NET Core 2.1 that prevents them updating to .NET Core 2.1. We intend to fix this issue in the .NET Core August 2018 update. Based on that timing, we will extend the .NET Core 2.0 EOL date to October 1, 2018. This extension should give those customers affected by this issues a rema...
The RyuJIT transition is complete!
RyuJIT is the code name for the .NET just-in-time compiler, one of the foundational components of the .NET runtime. In contrast, the Roslyn C# compiler compiles C# code to IL byte code. The RyuJIT compiler compiles IL byte code to machine code for multiple processors. With the recent merge of the dotnet/coreclr #18064 pull request, the remaining legacy code generation components (from older JIT implementations) have been removed from the RyuJIT source code. This PR removed almost 50k lines of code! All four of the processor architectures targeted by RyuJIT (x86, x64, ARM32, ARM64) are now built purely on the Ryu...
Staying up-to-date with .NET Container Images
This post describes the container images that we produce and update for you, that you can use with Docker, Kubernetes and other systems. When you are using .NET and Docker together, you are probably using the official .NET container images from Microsoft. We've made many improvements over the last year to the .NET images that make it easier for you to containerize .NET applications. Last week during DockerCon 2018, I posted an update about Using .NET and Docker Together. It demonstrates how you can use Docker with .NET, for production, development and testing. Those scenarios are all based on the .NET containe...