Your official information source from the .NET Web Development and Tools group at Microsoft.
I’m excited to show the new features of the ASP.NET and Web Tools for Visual Studio 2013 RC. Click here to download and install the Visual Studio 2013 RC today. Please check http://www.asp.net/vnext for release notes, documentation, and tutorials. This blog includes both the new RC features and the features that already announced in the ASP.NET and Web Tools for VS2013 Preview that was released 2 months ago. We will have incoming blogs to talk about the features in detail.
We made a simple UI for creating projects that offer support for multiple ASP.NET frameworks (Web Forms, MVC, and Web API). New features are available for Web Forms that used to be offered only for MVC, such as automatic test project creation different authentication configurations.
Different authentication configurations can be chosen, and authentication works the same in all ASP.NET frameworks and in web hosting software other than IIS.
For more information about the new process for creating web projects, see Creating ASP.NET Web Projects in Visual Studio 2013 RC.
A new feature, Browser Link, uses a SignalR channel between browsers and Visual Studio 2013 RC. It allows manually refreshing all connected browsers by clicking the toolbar refresh button. You can connect multiple browsers to your development site, including mobile emulators, and click refresh to refresh all the browsers all at the same time. In RC, we also introduced Browser Link Dashboard where you can refresh individual browser. You enable the Browser Link Dashboard from the refresh icon as shown in the following image:
We also released API to write browser link extensions. Mads’ web essentials for Visual Studio 2013 (source) contains a few extensions that one can find really useful.
In the Browser Link Dashboard, you can see each active connection listed under the Connections node. You can use the down arrow for each browser to choose a task, such as refresh to refresh each individual browser manually, or manual actions with the extensions that you’ve installed, such as “Design Mode”, “Inspect Mode”, “Snapshot Page”, “Start Recording” web essential extension commands.
The Problems node lists the possible reasons why the browser link might not work and offers suggestions to correct the problem.
In VS2013 RC, a new HTML editor is released for Razor files and HTML files. Web Forms .aspx, .master and user control .ascx files are still using the legacy editor for various reasons. The new HTML editor provides a single unified HTML5-based schema. It has some improvement such as automatic brace completion, jQueryUI and AngularJS attribute IntelliSense, attribute IntelliSense Grouping etc. In RC, we make CSS class attribute intelliSense working even if bundling and minification is used.
With installation of Azure SDK 2.1, you can create Windows Azure web sites from VS2013 RC’s server explorer.
You can easily configure the website, add a new Web Site, and import the subscription file (which is used to publish to Windows Azure from the Visual Studio).
VS 2013 RC has completely rewritten MVC Scaffolding. Please visit here for more information.
We removed WebForm Scaffolding from this release because it's not ready yet. We’ll put the new bits in future release, possibly targeting update 1.
MVC projects are now standard Web Applications and do not use their own project GUID. An MVC 5 project is created if the MVC checkbox is checked in the One ASP.NET new project dialog. For more information see Getting Started with ASP.NET MVC 5.
ASP.NET Web API 2 includes a variety of new features including:
· Attribute routing
· OData improvements
· Request batching
· Improved unit testability
· Support for portable libraries
· OWIN integration.
For details on ASP.NET Web API 2 features, please see the RC release notes or refer to the ASP.NET Web API 2 documentation here.
SignalR 2.0.0-rc1 is included with VS2013 RC. It includes support for MonoTouch and MonoDroid, portable .NET client, and the self-hosting package Microsoft.AspNet.SignalR.SelfHost, and it is backwards compatible for servers. For more SignalR 2.0.0-rc1 release notes, please visit http://www.asp.net/visual-studio/overview/2013/release-notes-(release-candidate)#TOC13 .
Entity Framework 6.0.0-rc1 is included with VS2013 RC. See http://blogs.msdn.com/b/adonet/archive/2013/08/21/ef6-release-candidate-available.aspx for detail.
The Microsoft OWIN components (also known as the Katana project) integrates support for the Open Web Interface for .NET (OWIN), deep into ASP.NET. OWIN defines a standard interface between .NET web servers and web applications. Any OWIN based application or middleware can run on any OWIN capable host, including ASP.NET on IIS.
You host OWIN-based middleware and frameworks in ASP.NET using the Microsoft.Owin.Host.SystemWeb NuGet package. The Microsoft.Owin.Host.SystemWeb package has been enhanced to enable an OWIN middleware developer to provide hints to the SystemWeb server if the middleware needs to be called during a specific ASP.NET pipeline stage (ex during the authentication stage). The Microsoft OWIN Components also includes an HttpListener-based server, a self-host API and an OwinHost executable for running OWIN applications without having to create a custom host. With the OwinHost 2.0.0-rc1 NuGet package, VS2012 RC can now easily convert an IIS Express based WebAPI or SignalR project to a project that is run from OwinHost.exe.
ASP.NET authentication is now based on OWIN middleware that can be used on any OWIN-based host. Microsoft OWIN Components includes a rich set of middleware components for authentication including support for cookie-based authentication, logins using external identity providers (like Microsoft Accounts, Facebook, Google, Twitter), and logins using organizational accounts from your on-premise Active Directory or Windows Azure Active Directory. Also included is support for OAuth 2.0, JWT and CORS. For more information see An Overview of Project Katana.
ASP.NET Identity is the new membership system for building ASP.NET applications. ASP.NET Identity makes it easy to integrate user specific profile data with the application data. With ASP.NET Identity you control the persistence model of your application. For example, you can store your user data in a SQL Server database or any other persistence store.
For information about using ASP.NET Identity with Individual User Accounts authentication, see http://www.asp.net/visual-studio/overview/2013/creating-web-projects-in-visual-studio#inauth.
NuGet 2.7 is included with VS2013 RC. See http://docs.nuget.org/docs/release-notes/nuget-2.7 for more details.
Today’s Visual Studio 2013 RC has a lot of useful features for developers using ASP.NET. Read the release notes to learn even more, and install it today!
@mojtaba, SQL Server CE is not supported in VS 2013. Please use visualstudio.uservoice.com if you want to suggest Visual Studio to take it back. Thanks for the support.
given explanation was understandable
Thanks for this valuable article. But I have a problem. I installed RC on Windows 7. There are No Connections in my Browser Link Dashboard. As I have seen in your image that there are two browsers connected in your RC, but I don't have a single one. What should i do?
@Nimit: For the connections to show up in the dashboard, you should navigate to some page in your app using F5, Ctrl +F5 or View in Browser. Do let me know if this does not work.
Please contact reshmim at Microsoft.com if you continue to see this. Thank you for trying out the new features!
In the OWIN section: "Also included is support for OAuth 2.0, JWT and CORS."
Any documentation on this anywhere?
Thnaks for posting this. really useful.
@Kevin Radcliffe - At the moment there is limited documentation on these topics. But they are on the way.
Very nice :)
Browser Link !! nice feature. Thank u
I have been some problem to install the VS 2013rc. I am getting some fatal error for framework 4.5. But I really like the web and the mobile view application of the version.