Announcing Updated Web Development Tools for ASP.NET Core RC2

We are pleased to announce the ASP.NET Core Tooling Preview release to support the .NET Core RC2 and ASP.NET Core RC2 release. Get the new version of the framework and Visual Studio 2015 support now at: http://dot.net

Support for .NET CLI

With the RC2 release of .NET Core, we introduced the .NET Command Line Interface to enable easy construction, package management, and compilation of applications using the new .NET Core SDK. However, this is Visual Studio and we deliver visual tools that make working with these tools easier. That’s exactly what we’ve done and packaged support for these tasks in Visual Studio to make use of the dotnet tool. From Visual Studio, when you use the standard compile tools you know and love, you will see in the output window the same commands execute if you were working with their applications directly on the command-line:

With this change in .NET tooling, we are also delivering support for the debugger to inspect your application just as you have with previous versions of ASP.NET.

Support for RC1 and RC2 projects

You will still be able to open your RC1 constructed projects in Visual Studio 2015. You should have in your global.json file an indicator of the version of the SDK in use to manage your project:

While the global.json file contains a version “1.0.0-rc1*” Visual Studio will enable the same compilation and management tools that you used for the RC1 version. If you remove this value from the sdk configuration option, or remove the sdk configuration option altogether, Visual Studio will start using the new .NET CLI tools with the RC2. This feature switch should help you upgrade your project from RC1 to RC2.

.NET Core Templates

Starting with this version of the web tooling, we are introducing a separation of the templates for .NET Core and the .NET Framework. When you enter the new project dialog, you will now be prompted to choose a template and framework just as you do any other project type:

There is also a complete section of templates on the left dedicated to the .NET Core framework. In this area, you can choose to start with a template to build a .NET Core base web application, .NET Core command-line application, or a .NET Core compatible class library that compiles to a NuGet package.

Support for Authentication and Authorization in Web API

During the construction of a new Web API project, you can now opt to activate authentication capabilities using Active Directory or the Work and School accounts options:

This has the effect of placing an AuthorizeAttribute on the template generated controller, and you can further define your security policy in the Startup.cs file for your application.

Summary

This is a significant set of changes to support the new .NET Core and ASP.NET project systems and runtimes in Visual Studio 2015, and we’re just getting started. With this release, you have an updated go-live license for this version of the ASP.NET runtime and libraries. We will continue to evolve the editor capabilities in Visual Studio to further support these new project types. Get a copy of this update for Visual Studio now from http://dot.net

Jeff Fritz, Program Manager, .NET Developer Outreach Team

Jeff is a long time web developer, systems architect and survivor of the dot-com bust. With a history of almost 15 years delivering multi-tenant web applications in the financial, pharmaceutical, and education industries, Jeff has a long history of large-scale successful web application launches. You can learn more from Jeff on his blog at www.jeffreyfritz.com and on twitter at @csharpfritz

I updated an ASP.Net V5 RC1 project to .Net Core 1.0. The project happens to have a number of node modules that have files with .cs extensions. The Preview1 tooling now tries to compile those source files. The entire node_modules directory used to be excluded and still needs to be.

I had the same problem with the templates not appearing after me installing the SDK/runtime. Looks like we need to install the tooling separately (https://www.microsoft.com/net/core#windows) as it’s not included with the SDK installer.

If you installed VS 2015 Update 3 before the tooling preview then there’s probably a problem with registry entries pertaining to the VC++ 2015 redistributable, which is causing the installer for the tooling preview to fail.

When I open new project templates in Web category I see 3 option.
First one is for .net 4xx etc… (old one)
Other two;
“ASP.Net Core Web application (.Net Core)”
“ASP.Net Core Web application (.Net Framework)”

What is the difference between them ?
If I am going to start new project I should start with (.Net Core)
And if I have a MVC 5 + .Net 4xx clas library solution I can add “ASP.Net Core Web application (.Net Framework)” to replace old MVC 5
project so I can still use class libraries developed with .Net 4xx ??

2 years ago

Tony

There is no MVC tooling available yet? I don’t see any of the context menu options for “Create Controller”, “Create View”, “Go to View”, etc.

If have started a new project (web-application) with RC1 and had to stop it, as SqlClient wasn’t implemented fully.
E.g. DataTable was not implemented.
=> Are the objects of System.Data.SqlClient implemented fully in RC2 now?
Thanks for a feedback.

2 years ago

Saad

Is there an offline version of the tooling preview available?
I have a system that isnt connected to the internet and I need to install the tooling preview but cant find any offline isntaller

2 years ago

Martin

Good question @ilker. Can someone explain the difference between these new templates “ASP.Net Core Web application (.Net Core)”
“ASP.Net Core Web application (.Net Framework)”. If i choose “.Net Framework” then if have the full .net 4.6.1?

2 years ago

Mohan

Guys, Is there any reason why the individual user accounts based authorization not enable for Web API templates in Core. It is available for Asp.Net (4.5) versions. Please comment.

2 years ago

Peter

VS 2015 Community Edition notified me that the update is available, so I clicked update and the browser opened then downloaded “DotNetCore.1.0.0.RC2-VS2015Tools.Preview1.exe”. I closed all VS windows and run the update file. Now stuck at “Microsoft Visual Studio Preparation” for 10 minutes already. What should I do?

2 years ago

Pranav

After Installation of Visual Studio 2015 Update 3 I tried installing VS tools 2015 Preview 2 and instillation always fails. I tried every possible combination from repair, uninstall, install of Visual Studio 2015 to repair, uninstall, install of preview 2. I always get below error in event viewer. Any help will be highly appreciated.