.NET Blog
Free. Cross-platform. Open source. A developer platform for building all your apps.
Featured posts
Announcing .NET 10
Announcing the release of .NET 10, the most productive, modern, secure, intelligent, and performant release of .NET yet. With updates across ASP.NET Core, C# 14...
Latest posts
ASP.NET MVC Security Bulletin MS14-059 ships to help secure .NET NuGet Libraries
Microsoft Security Bulletin MS14-059 – Important: Vulnerability in ASP.NET MVC Could Allow Security Feature Bypass (2990942) This is the first release from Microsoft that uses Security Updates for .NET NuGet Libraries Support. This feature enables Microsoft to update app-deployed .NET NuGet libraries, for machines with the .NET Framework 4.5.1 or later version installed. This security bulletin was released on 10/14/2014 as part of the monthly “patch Tuesday”. This security update is rated “Important” for the ASP.NET MVC 2.0, ASP.NET MVC 3.0, ASP.NET MVC 4.0, ASP.NET MVC 5.0, and AS...
ASP.NET Identity 2.2.0-alpha1
We are releasing a preview of ASP.NET Identity 2.2.0-alpha1. The main focus in this release was to fix bugs and address performance issues.Download this releaseYou can download ASP.NET Identity from the NuGet gallery. You can install or update these packages using the NuGet Package Manager Console, like this:Install-Package Microsoft.AspNet.Identity.EntityFramework –Version 2.2.0-alpha1 -pre Install-Package Microsoft.AspNet.Identity.Core -Version 2.2.0-alpha1 -preInstall-Package Microsoft.AspNet.Identity.OWIN -Version 2.2.0-alpha1 –preWhat’s in this release?Following query has the list of ...
Package Manifests
As we work on the designs for getting NuGet in the platform, it has become clear that NuGet needs better support for carrying arbitrary artifacts in packages and exposing them for consumption after the initial package installation. Conventional Manifests Since NuGet's initial release, it has supported conventional manifests and only a few concepts. All other files inside the package are completely ignored and NuGet's existing design makes it difficult to expand on these concepts or introduce new ones. Before we dive into where we think NuGet is going, let's look closer at what NuGet supports today wit...
Microsoft Asp.Net MVC Security Update MS14-059 broke my build!
Microsoft just released a new security update to be automatically applied to machines configured to use Microsoft Update. The security bulletin is available here: https://technet.microsoft.com/en-us/library/security/ms14-059Unfortunately, some ASP.NET MVC 3 and 4 VS projects can no longer build after the update is applied. These projects will fail with the following error: Could not locate the assembly "System.Web.Mvc,Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35,processorArchitecture=MSIL".This happens when your project references assemblies from the GAC or the Reference Assemblies...
Announcing new Web Features in Visual Studio 2013 Update 4 RC
Today, the Visual Studio team announced the release of Visual Studio 2013 Update 4 RC. Our team added a few useful features and did some bug fixing in this update to improve the web development experience. Microsoft ASP.NET and Web Tools 2013.4 RC JSON Editor Improvement We made a few improvements in the JSON editor, including performance improvements such as loading the JSON schema asynchronously, caching child schemas, improving IntelliSense, etc. We also have the following new features: JSON Schema validation We added a JSON schema validation feature, based on the schema selected in the drop-down li...
NuGet: In the Platform
I recently declared that NuGet is "Broken By Design." Now, that was hyperbolic; I don't really think NuGet is broken. In fact, I'm very pleased with NuGet (and proud of it). But I wanted to make the point that NuGet's approach both earned it success but also came at a cost. NuGet can't presently offer some expected package management features because it's merely a package management façade over top of existing Visual Studio and MSBuild capabilities. I also wanted you all to know that we recognize that NuGet has been stagnating and that we want to make some changes. The Right Approach? For years, many have ques...
October 2014 .NET Security Updates
The .NET team released a security bulletin today as part of the monthly “patch Tuesday” cycle. Microsoft Security Bulletin MS14-057 - Critical, Vulnerabilities in the .NET Framework could allow remote code execution (3000414) This security update resolves three privately reported vulnerabilities in Microsoft .NET Framework. The most severe of these vulnerabilities could allow remote code execution if an attacker sends a specially crafted URI request containing international characters to a .NET web application. The security update further resolves an Elevation of Privilege vulnerability in the...
Announcing Microsoft.ASPNET.Facebook 1.1 RTM
![Kirthi [MSFT]](https://devblogs.microsoft.com/dotnet/wp-content/uploads/sites/10/letter-avatar/212fc64ade75a0dd26ca06c5ceb2e6e3.svg){kind=avatar}
The NuGet packages for Microsoft.ASPNET.Facebook 1.1 are now live on the NuGet gallery!Download this releaseYou can install or update the NuGet packages for Microsoft.ASPNET.Facebook 1.1 using the NuGet Package Manager Console, like this: What’s in this release?In this release, we enabled better support for the Safari browser and added a new feature that gives developers the ability to add custom logic for browsers that do not have cookies enabled. You can find detailed explanation for the new features here. The Visual Studio template that uses this updated package will be released soon. The Visual Studi...
_references.js file’s auto sync feature
In VS2013 RTM, we shipped a not well known feature for _references.js file: /// <autosync enabled="true" />. If we specify /// <autosync enabled="true" /> in the beginning of ~/scripts/_references.js, then any addition, rename, deletion of JavaScript files in the project will automatically change the content in this file. You can disable this feature by removing the line or put assign false to enabled attribute. For example, create a new MVC project, open scripts/_references.js file and you will see the following if you are using VS2013 with update 3. Drag and drop bootstrap....