.NET Blog
Free. Cross-platform. Open source. A developer platform for building all your apps.
Featured posts
Announcing .NET 10 Release Candidate 1
.NET 10 Release Candidate 1 is available with improvements across the runtime, SDK, libraries, ASP.NET Core, Blazor, .NET MAUI, and more!
Latest posts
The Changelog interview on open sourcing .NET
![Rich Lander [MSFT]](https://devblogs.microsoft.com/dotnet/wp-content/uploads/sites/10/letter-avatar/cb895f2fa6fae6447bab144d4f3ec4b3.svg){kind=avatar}
We recently talked to Adam and Jared at The Changelog about open sourcing .NET Core. Check out the show. #134: Open Sourcing .NET Core with the Microsoft .NET team Here's the introduction from The Changelog: This week, we have members from .NET core team at Microsoft on the show to discuss Microsoft’s motivation for open sourcing the base class libraries of .NET, open source vs source open, the true goal of open sourcing .NET Core, and more. “As far as open source goes, one of the key things that we need to focus on is being able to not just release source, but also take contributions bac...
Channel 9 interview on open sourcing .NET
Curious to where we are with open sourcing .NET Core? Do you want to know which libraries are next? Interested in a white boarding session with David Kean? Then you should check out this video on Channel 9: Questions or concerns? Leave a comment on the Channel 9 post.
Introducing .NET Core
At connect(), we announced that .NET Core will be entirely released as open source software. I also promised to follow up with more details on .NET Core. In this post, I’ll provide an overview of .NET Core, how we’re going to release it, how it relates to the .NET Framework, and what this means for cross-platform and open source development. Looking back – motivating .NET Core First let’s look back to understand how the .NET platform was packaged in the past. This helps to motivate some of the decisions and ideas that resulted in the creation of .NET Core. .NET – a set of verticals When we originally shipped ...
Introducing the NuGet PowerShell Commands Survey
You've probably seen the cool announcements from Microsoft about the new Community Edition of Visual Studio and the upcoming Visual Studio 2015 release in the new year. We at the NuGet team have been ramping up our tools to support the new Visual Studio with a better visual experience and a better command-line experience. We've also released some information about our upcoming v3 release of our protocol based on JSON-LD. Now we want to do something to stay true to the open-source license of our tool. We want to ask you for your input about our PowerShell capabilities. We will review all feedback and make decisio...
Advisory Council Proposal — Call for Community Feedback Extended to December 5th
This is a cross post from the .NET Foundation blog and written by Gianugo Rabellino. --ImmoThe increased openness of .NET has sparked widespread interest in the .NET Foundation. As a result, its Board of Directors has decided to extend the timeframe for community feedback on the .NET Foundation Advisory Council to December, 5, 2014. The Advisory Council will bring unique knowledge and skills to complement our Board to more effectively govern the organization. The community has already helped shape the role of the Foundation – a new organization that already includes more than 30 projects across t...
Content negotiation in MVC 6 (or how can I just write JSON)
[Update] - We decided to make two significant changes starting with Beta3, we are to not include the XML formatter by default, as well as special treat browsers. The content below is still relevant up to MVC 6 Beta2.IntroIn this blog, I intend to provide a simplified how-things-work and how-to-change-the-behavior. It is not intended as a deep dive into content negotiation.Since Web API 1 controller code can return an object of an arbitrary type and the framework will send it as JSON or XML to the client. The process of picking the output format is called “content negotiation”. The basic rules can be d...
One Week of Open Source
Last Wednesday, we announced the new .NET 2015 Preview and our plans to fully open source .NET Core. What an awesome week! Thank you! We knew that you guys would really dig open source but we didn’t expect such a positive response. Within a single week, our open source blog post got more than 200k views! And even on GitHub, which seems to be the place for open source these days, .NET Core jumped at the top of the trending GitHub repositories for last week. We also have seen a tremendous activity in our social channels, specifically Twitter, blog comments and our Facebook site. I’ve seen very few ...
Katana, ASP.NET 5, and bridging the gap
This post is for developers that have been using the Microsoft Owin components (e.g. the Katana project) and want to know how it relates to ASP.NET 5.As discussed in Katana’s roadmap, the next major version of Katana is being fully integrated into ASP.NET 5. This integration has resulted in several changes that make Katana v3.0 based components not directly compatible with 5. Developers and consumers of v3.0 based components may choose to fully migrate their components or use OWIN to help bridge the gap.MigrateDevelopers may choose to update their components to integrate directly with ASP.NET 5. ASP.NET 5 b...
.NET Core is Open Source
Today is a huge day for .NET! We’re happy to announce that .NET Core will be open source, including the runtime as well as the framework libraries. This is a natural progression of our open source efforts, which already covers the managed compilers (C#, VB, and F#) as well as ASP.NET: This takes it to the next level by extending it to the .NET runtime and the core framework. What is .NET Core? .NET Core is a modular development stack that is the foundation of all future .NET platforms It’s already used by ASP.NET 5 and .NET Native. I’ll go into more detail on what NET Core ...