.NET Blog
Free. Cross-platform. Open source. A developer platform for building all your apps.
Featured posts
Aspire 9.4 is here with a CLI and interactive dashboard features
Aspire 9.4 is packed with new features, integrations, and improvements
Latest posts
Where can you meet the team? November 2014 at AngleBrackets and TechEd
We on the Web Tools team love hanging out with the community. We thought it would be cool to start sharing exactly where we will be and what conferences or user groups you can join us at!The .NET Developer Blog has a great always updated list of .NET User Groups, so be sure to bookmark that also!We’ve got two big events coming up soon, and there is still time to register! We’ll post to the this blog each month with our list of exciting events. Make sure you’ve subscribed!
Announcing October 2014 Updates to .NET Framework vNext, ASP.NET vNext and .NET Native in Visual Studio “14” CTP4
Updated (2017): See .NET Framework Releases to learn about newer releases. Today, we are announcing updates to the .NET Framework vNext, ASP.NET vNext and .NET Native. These are all available in Visual Studio “14” CTP4. This .NET Framework release contains RyuJIT, the next generation X64 JIT. ASP.NET vNext contains major improvements in the runtime and Visual Studio Experience. Additionally, .NET Native contains a small set of fixes for reported issues. Please download these .NET releases with Visual Studio “14” CTP4 and give us feedback. .NET Framework vNext Today’s release of .NET Framework vNext adds RyuJIT a...
ASP.NET vNext in Visual Studio “14” CTP 4
Today we released updates for ASP.NET vNext in Visual Studio “14” CTP 4. This release includes the ASP.NET vNext runtime and tooling improvements as outlined below. ASP.NET vNext Runtime This CTP includes our alpha4 runtime packages for ASP.NET vNext. You can find details on the specific enhancements added and issues fixed in the published release notes on GitHub. For information on how to get started with ASP.NET vNext using Visual Studio “14” check out the article Getting Started with ASP.NET vNext and Visual Studio "14". The MVC Music Store and Bug Tracker sample projects have been ...
Discontinuing Updates for Visual Studio 2010
As we work on some big changes for NuGet 3.x, we're finding that we're at a crossroads: Should we use .NET 4.5 and improve our Visual Studio UI using new features available in Visual Studio 2012, Visual Studio 2013, and Visual Studio "14"; or should we retain support for Visual Studio 2010? Visual Studio 2010 has been supported since NuGet's introduction. But supporting it prevents us from using .NET 4.5 and since it has different visual styling from the newer versions of Visual Studio, it's holding us back on some of our new UI. Visual Studio 2010 Usage In July 2013, we started capturing what version of Visua...
Target Framework Filtering and a Pending Breaking Change
Have you ever seen this error before? Doesn't it make you want to yell and scream at NuGet, "Why did you just show it to me if I couldn't install it!?‽" Yeah, it makes us want to yell and scream too, so we decided to set about fixing it! Along with that, we've also discovered a bug we want to correct but unfortunately, it's a breaking change so we wanted to get your feedback and do it in NuGet 3.0. Target Framework Filtering in Search We are deploying a change to make the nuget.org Search API filter out packages (and versions of packages) that are incompatible with the framework your project targets. This m...
The Ajax Control Toolkit are now maintained by DevExpress
The open sourced Ajax Control Toolkit now has a new owner: DevExpress. This project was created on codeplex in 2007 and our team has been sponsoring its development ever since. It has been downloaded millions of times and played an important role in the field. The ASP.NET team knows that many people use the ASP.NET Ajax Control Toolkit and that it continues to be updated to work with modern browsers. We are happy to announce that DevExpress has stepped up to be the project owner for the toolkit and is in the process of making sure it is easy to install, works with modern browsers and continues t...
.NET Micro Framework now supports Visual Studio 2013
Today the .NET Micro Framework team is releasing a beta update of the .NET Micro Framework SDK that adds support for Visual Studio 2013. The release also contains other improvements that will benefit developers and hardware partners, making the install and update experience better. Check out the .NET Micro Framework Team blog, and the Netmf.com site to learn more about .NET Micro Framework and this release. Read the Microsoft Open Technologies blog to learn more about this open source project and community engagement. You can download the .NET Micro Framework SDK 4.3.1 (SDK R2 Beta) update from our project site...
.NET Micro Framework now supports Visual Studio 2013
Today the .NET Micro Framework team is releasing a beta update of the .NET Micro Framework SDK that adds support for Visual Studio 2013. The release also contains other improvements that will benefit developers and hardware partners, making the install and update experience better. Check out the .NET Micro Framework Team blog, and the Netmf.com site to learn more about .NET Micro Framework and this release. Read the Microsoft Open Technologies blog to learn more about this open source project and community engagement. You can download the .NET Micro Framework SDK 4.3.1 (SDK R2 Beta) update from our project site...
Supporting Semantic Versioning 2.0.0
Updated Sept. 2015: Our roadmap and requirements have changed and we have yet to implement these features as of NuGet v3.2. We are tracking this issue on GitHub. Please track this issue to follow our progress. We adopted Semantic Versioning (SemVer) in NuGet 1.6. At the time, SemVer 1.0.0 was the current version of the spec. Adopting SemVer provided NuGet support of pre-release package versions. Since introducing SemVer support, SemVer has reached 2.0.0 and introduced some new features. There have been [a lot]() of requests for NuGet to support SemVer 2.0.0 so these features can be used. We've ...