.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
Redesigning the NuGet Websites
Blog Redesign is LIVE! What better way to announce upcoming website redesigns than by implementing that redesign on our blog? Earlier today, we deployed changes to http://blog.nuget.org that apply a new visual design that we expect to carry over to the docs and gallery sites too. Redesign Goals The goals of the redesign effort are manifold. Here are some of our high-level desires for the websites: Consistency Across Gallery, Documentation, and Blog With this deployment to the blog, our three sites are now quite inconsistent. The blog has the new look while the documentation and gallery sites still ha...
ASP.NET 4.5.2 and EnableViewStateMac
Please note: This post is now outdated. See http://blogs.msdn.com/b/webdev/archive/2014/09/09/farewell-enableviewstatemac.aspx for the most up-to-date information. A few months ago, we posted that we were making changes to the way EnableViewStateMac behaves in ASP.NET. I’ll forego the typical blog post ceremony and cut right to the chase: starting with ASP.NET 4.5.2, the runtime enforces EnableViewStateMac=true. If an application sets <%@ Page EnableViewStateMac="false" %> as a directive or <pages enableViewStateMac="false" /> as a config setting, the runtime ignores it and pretends that the ...
Announcing the .NET Framework 4.5.2
Updated (2017): See .NET Framework Releases to learn about newer releases. Updated (July 2015): See Announcing .NET Framework 4.6 to read about the latest version of the NET Framework. We are happy to announce the availability of the .NET Framework 4.5.2. It is a highly compatible, in-place update to the .NET Framework 4, 4.5 and 4.5.1. You can download the releases now, We incorporated feedback we received for the .NET Framework 4.5.1 from different feedback sources to provide a faster release cadence. In this blog post we will talk about some of the new features we are delivering in the .NET ...
Get your libraries ready for Windows Phone 8.1
Two weeks ago, we released the Windows Phone preview for developers. In this post, I’ll cover what this means for library and app developers. What this means for library developers As a .NET developer you can target Windows Phone 8.1 via two platforms: Apps that target Windows Phone Silverlight 8.1 can consume existing libraries and NuGet packages as-is – after all, it’s still Windows Phone Silverlight – just an updated version. Apps that target the new Windows Phone 8.1 platform can only consume libraries and NuGet packages that are built for Windows Phone 8.1. But don’t worry ...
Introducing the Microsoft .NET Framework Repair Tool
The .NET Setup team has made some significant investments over the last couple of years in improving the deployment experience for the .NET Framework setup and its updates. In spite of this effort, occasionally some customers run into issues deploying the .NET Framework or its updates that cannot be fixed from within the setup itself. For such cases, we have a tool - the .NET Framework Repair Tool that can help with detecting and fixing some of these common causes of install failures. We are happy to announce a new version of the tool that encompasses support for all versions of the .NET Framework fro...
.NET Native Performance
This post was authored by Xy Ziemba, the Program Manager for .NET Native performance, and Andrew Pardoe, Program Manager on the .NET runtime team. In our previous blog post introducing .NET Native, we talked about how .NET Native gives you the performance of C++ with the productivity of C#. Putting that in quantitative terms, Windows Store apps compiled with .NET Native start up to 60% faster and use up to 25% less reference set compared to when the apps are compiled with NGen. This means your users get into your app even faster after a tile tap! While developing .NET Native, we made a number of design choices ...
.NET Native Performance
This post was authored by Xy Ziemba, the Program Manager for .NET Native performance, and Andrew Pardoe, Program Manager on the .NET runtime team. In our previous blog post introducing .NET Native, we talked about how .NET Native gives you the performance of C++ with the productivity of C#. Putting that in quantitative terms, Windows Store apps compiled with .NET Native start up to 60% faster and use up to 25% less reference set compared to when the apps are compiled with NGen. This means your users get into your app even faster after a tile tap! While developing .NET Native, we made a number of design choices ...
.NET Native Performance
This post was authored by Xy Ziemba, the Program Manager for .NET Native performance, and Andrew Pardoe, Program Manager on the .NET runtime team. In our previous blog post introducing .NET Native, we talked about how .NET Native gives you the performance of C++ with the productivity of C#. Putting that in quantitative terms, Windows Store apps compiled with .NET Native start up to 60% faster and use up to 25% less reference set compared to when the apps are compiled with NGen. This means your users get into your app even faster after a tile tap! While developing .NET Native, we made a number of design choi...
Building NuGet 3.x
Evolution of NuGet At MonkeySpace 2013 last July, we revealed some of our thinking for the Evolution of NuGet. These were the ideas we had for what would become NuGet 3.x and they included the following areas: Package Discovery Package Trust / Incompatibility API Package Installation / Build Making Progress The full list is a pretty tall order but we're making progress toward these goals. In fact, since giving that talk in July 2013, here are some of the features that have been released: Beyond this, the team has been concentrating on the RESTful API v3 architecture and...