.NET Blog
Free. Cross-platform. Open source. A developer platform for building all your apps.
Featured posts
.NET Aspire 9.3 is here and enhanced with GitHub Copilot!
.NET Aspire 9.3 is the biggest release of .NET Aspire yet, with the introduction of GitHub Copilot directly into the .NET Aspire Dashboard, updates for integrat...
Latest posts
The future of Unity
This post was written by Christopher Bennage (@bennage), a member of the Microsoft patterns & practices team.A few months ago, we announced that we were handing Prism over to new owners. We put a lot of time and effort into identifying owners that would invest in the project and support the community.Today, we are announcing a similar transition of ownership for Unity.The new owners for Unity are:Pablo Cibraro. Pablo is an internationally recognized expert with over 15 years of experience in designing and implementing large distributed systems with Microsoft technologies. For the last 9 years Pablo has helped...
ASP.NET Community Standup – August 18, 2015
This is the next in a series of blog posts that will cover the topics discussed in the ASP.NET Community Standup. The community standup is a short video-based discussion with some of the leaders of the ASP.NET development teams covering the accomplishments of the team on the new ASP.NET 5 framework over the previous week. Within 30 minutes, Scott Hanselman, Damian Edwards, Jon Galloway and an occasional guest or two discuss new features and ask for feedback on important decisions being made by the ASP.NET development teams. Each week the standup is hosted live on Google Hangouts and the team publishes the re...
Gen2 free list changes in CLR 4.6 GC
I wanted to mention this because I started seeing posts about it. In 4.6 we improved the way we use the gen2 free list to promote gen1 survivors into. Unfortunately there was a perf bug that I didn’t notice till it was fairly late so it wasn’t approved to be checked into 4.6 at the time. Now that I am seeing more people hitting it, I have checked the fix into the next hotfix rollup for 4.6 which you will be able to download when it’s released in the near future (I will update the exact location when it’s available). The symptom for this bug is that you are seeing GC taking a lot longer th...
August 2015 .NET Security Updates
The .NET team released two security bulletins today as part of the monthly "Update Tuesday" cycle. Microsoft Security Bulletin MS15-080 - Critical, Vulnerability in .NET Framework Could Allow Remote Code Execution (3078662) This security update resolves vulnerabilities in Microsoft .NET Framework. The most severe of the vulnerabilities could allow remote code execution if a user opens a specially crafted document or visits an untrusted webpage that contains embedded TrueType or OpenType fonts.This security update is rated Critical for Microsoft .NET Framework 3.0 Service Pack 2, Microsoft .NET...
NuGet 2 code base moves to GitHub
In the last few months we have constantly moved the issues and all new code base to GitHub. Today we moved the last bits of code from CodePlex to GitHub. We have stopped monitoring the CodePlex site completely, and will not be taking further looks at reports there or pull requests. As we keep working on NuGet 3.1.2 release for Visual Studio 2015 we will also work on 2.8.7 release with bug fixes for Visual Studio 2013. The tip branch we compile nuget.core from is the dev branch, this is a change from master we used in CodePlex. The change it to align this repo with the rest of the repos in nuget.org.
[Guest post] Visual F# Power Tools: community-led tooling for F# in Visual Studio
![Visual FSharp Team [MSFT]](https://devblogs.microsoft.com/dotnet/wp-content/uploads/sites/10/letter-avatar/8aba62e0c2d790d7cfc56493b82432e4.svg){kind=avatar}
This is a guest post by Anh-Dung Phan and Vasily Kirichenko, F# community developers and contributors to the superb Visual F# Power Tools extension for Visual Studio. – Visual F# Team We are pleased to tell you about the Visual F# Power Tools, a Visual Studio extension aimed at providing extended tooling for F# in Visual Studio. You can download it today from the Visual Studio gallery. The goal of the extension is to complement the standard Visual Studio F# tooling by adding missing features such as semantic highlighting, rename refactoring, find all references, metadata-as-source, and more. What’s part...
Universal Windows apps in .NET
![Rich Lander [MSFT]](https://devblogs.microsoft.com/dotnet/wp-content/uploads/sites/10/letter-avatar/cb895f2fa6fae6447bab144d4f3ec4b3.svg){kind=avatar}
This post was written by Lucian Wischik, a Program Manager on the Managed Languages team. We just released the Universal Windows app development tools for writing Windows 10 apps in Visual Studio 2015. It is an exciting release: you can now use the latest .NET technology to build Universal Windows Platform ("UWP") apps that run on every Windows device - the phone in your pocket, the tablet or laptop in your bag, the PC on your desk, the Xbox console in your living room, and all the new devices that are being added to the Windows family like HoloLens, Surface Hub, and IoT devices like the Raspberry Pi 2. Install...
Announcing NuGet 3.1 with Support for Universal Windows Platform
Today the NuGet team in collaboration with several other teams at Microsoft is happy to announce the release of a new version of the NuGet clients supporting the Universal Windows Platform and the new Portable class libraries. The NuGet tools are available through Tools->Extensions and Updates->Update tab in Visual Studio 2015 as well as from our GitHub repository. Additionally, we have released a new version of the NuGet command-line tool that you can download from NuGet.org. In this post, we will review the new capabilities that package authors can use and the process that windows programmers need to fol...
RyuJIT Bug Advisory in the .NET Framework 4.6
A code generation (AKA "codegen") issue in RyuJIT in the .NET Framework 4.6 has been discovered that affects a calling pattern called Tail Call Optimization. The RyuJIT team has fixed the issue and has started the process of producing a .NET Framework 4.6 patch that will be freely available for anyone to download and install. There is a workaround for this issue, with the .NET Framework 4.6. It is supported to use this workaround in production to safely avoid this issue. The workaround is enabling a RyuJit config switch to disable tail call optimizations. See the recommendation below, for a detailed explanation ...