.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
September 2014 .NET Security Updates
The .NET team released a security bulletin and a security advisory today as part of the monthly “patch Tuesday” cycle. Microsoft Security Bulletin MS14-053 - Important, Vulnerabilities in .NET Framework Could Allow Denial of Service (2990931) This security update resolves one privately reported vulnerability in Microsoft .NET Framework. The vulnerability could allow denial of service if an attacker sends a small number of specially crafted requests to an affected .NET-enabled website. By default, ASP.NET is not installed when Microsoft .NET Framework is installed on any supported editi...
Using WCF in .NET Native
This post was authored by Ron Cain, a Software Development Engineer on the WCF team. In our previous post, we mentioned that some of the client components of Windows Communication Foundation (WCF) had been made available for .NET Native Windows Store apps in Visual Studio "14" CTP3. In this post, I will describe how to build a sample WCF Windows Store App using CTP3 and make it run using the .NET Native compiler. Note that most of this walk-through is not unique to .NET Native and applies equally well to a conventional Windows Store App. The final section of the walk- through describes the extra couple steps to...
Announcing the Release Candidates for Web API OData 5.3
The release candidate NuGet packages for ASP.NET Web API OData 5.3 are now live on the NuGet gallery!Download this releaseYou can install or update the release candidate NuGet packages for ASP.NET Web API OData 5.3 using the NuGet Package Manager Console, like this: What’s in this release?This release primarily includes great new features for Web API OData v4 as summarized below:ASP.NET Web API OData 5.3 Release Candidate Additional DocumentationTutorials and other information about Web API OData are available from the ASP.NET web site (http://www.asp.net/web-api/overview/odata-support-in-aspn...
Being an intern on the .NET Team
This summer we had six amazing interns that joined the team to work on .NET. Their projects ranged from internal tools, over shipping components to designing forward looking aspects: If you're interested in interning with Microsoft, visit our recruiting web site. Now let's dive right in and see what cool stuff they helped us building. Shaun Arora: Designing .NET for NuGet We're releasing more and more .NET framework functionality via NuGet. Moving forward, we intend to bring the two even closer together. Shaun spend a lot of time thinking about this problem space and helped us shape our thoughs and design...
Customizing Web API controller selector
In the last few weeks we have encountered a customer reports of performance issues with their Web API applications. When the 4th report exhibited the same phenomenon I figured it’s time to blog about it. Why would you customize a controller selector? (hint – try not to) It gives you a chance to control how the request gets routed. By default Web API uses the controller token from routing to select the controller. If you want a different behavior, such as selection based on an HTTP header, then you need to customize the controller selector. Wait. Not really. This was true for Web API 1.0. In Web API 2.0 a...
Command line scaffolding for ASP.NET vNext
In previous releases we have added support for scaffolding controllers/views based on project artifacts in both MVC and Web Forms projects. The technology used for those previous releases was tied to Visual Studio. With ASP.NET vNext one of our high level goals is to enable Visual Studio customers to work with non-Visual Studio users. So the most critical aspects of developing/testing ASP.NET vNext projects should be available to the non-Visual Studio. Scaffolding is a good example of this. Because we need to support scaffolding content into a project for both VS and non-VS scenarios we have gone back to the dra...
Announcing RTM of Katana 3
Dear all,Today I have the honor and privilege of announcing the general availability of Katana 3!This is an important update to Microsoft’s OWIN implementation, which offers you powerful new functionality. In a nutshell: You can find the new packages in the stable feed of NuGet.org. For a complete list please see this page. The preview stage is finally over: if you were holding back from using those packages given their prerelease status, you can now deploy in production with confidence. You can find the samples at the usual location https://aspnet.codeplex.com/. For samples demonstrating use of Kat...
A New Package Statistics Warehouse
The Warehouse is Dead, Long Live the Warehouse! Back in June, we blogged that our package statistics were full of lies. We made a fix and expected reports to become correct on June 26th. When June 26th came and went though, we discovered that the numbers were still questionable. Since then, we've identified a few other issues leading to invalid statistics, and we've made notable improvements to our statistics system. We are now confident that the statistics are trustworthy. As part of the work, we decided to discard our existing package statistics warehouse database and create a new one. This new warehouse woul...
Upgrading to jQuery.UI.Combined 1.11.0
The jQueryUI team released a new version of their library recently. This release has some changes which will impact your apps as you migrate to 1.11.0. This post will highlight the changes you need to do to use jQuery.UI.Combined NuGet package.ChangesI am going to highlight the change that is relevant to this post. For a full list of changes/ release notes see the changelog and upgrade guide on the jQueryUI team site.The jQuery.UI.Combined NuGet package combines the jQueryUI controls and a base theme. In 1.11.0, the jQuery UI team has renamed the files in the base theme. The change was to drop “jquery...