Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

VS 2015. Setting right target framework for ASP.NET 5 web project

I've created new ASP.NET 5 MVC project in Visual Studio 2015. On project creation wizard I've chosen to show the templates for .NET framework 4.6 and then on the next screen selected "Web Application" from ASP.NET 5 Preview Templates.

However, after creation it appears that the project listed only "dnx451" and "dnxcore50" in "frameworks" section of project.json:

  "frameworks": {     "dnx451": { },     "dnxcore50": { }   }, 

I've tried to change "dnx451" to "dnx46". The project has been built well but when I tried to run it, I got the following error message:

The current runtime target framework is not compatible with '...'.

Current runtime Target Framework: 'DNX,Version=v4.5.1 (dnx451)' Type: CLR Architecture: x86 Version: 1.0.0-beta5

How is it possible to change that "target framework" for ASP.NET 5 project?

Here is my global.json now:

{   "projects": [     "src",     "test",     "wrap"   ],   "sdk": {     "version": "1.0.0-beta5",     "runtime": "clr",     "architecture": "x86"   } } 

but it does not really matter what is listed there. I've already tried different builds of 1.0.0-beta5 and the latest 1.0.0-beta6

like image 626
Sergiy Avatar asked Jul 28 '15 09:07

Sergiy


People also ask

Which .NET Framework should I target?

I would recommend moving to the . Net 4.0 Client Profile. Although it doesn't have a large install base yet, it's a small download that your users can easily install. If you don't want your users to need to download the framework, you should target 3.5, which most people already have.

What .NET Framework comes with Visual Studio 2015?

Microsoft made it official today and released Visual Studio 2015 and . NET Framework 4.6, both fairly comprehensive and worked out and tested versions of the developer tools platforms meant for designing apps and services that work across various OSes and cloud-enabled environments.


1 Answers

The problem is that DNX is aware that your project is targeting dnx46 but IIS is not :). So, IIS is starting as .NET 4.5.1 (by default) and trying to load your project which isn't compatible with 4.5.1.

In a future version of the VS Tooling, we're going to do a better job of detecting that but until then, things are a little rough for Web Applications that want to target .NET versions above 4.5.1. For now, I suggest just using dnx451 until then (if you aren't depending on .NET 4.5.2/4.6 functionality), but I'll provide some instructions below on how to make this work today if you need to use 4.5.2 or higher.

Note: dnx452 and dnx46 are fully supported in Console Applications and when using servers other than IIS (such as Kestrel or WebListener). Basically anything you can launch using the native dnx.exe bootstrapper works with dnx451 and dnx46 but the other hosting environments (IIS, IIS Express) need additional hints to launch the correct framework.

To make this work today, you need to set an environment variable DNX_IIS_RUNTIME_FRAMEWORK to the target framework you want to use. You can do this in the Project Properties page for the web application, on the Debug tab. Just choose the IIS Express profile and add the environment variable as below:

Launch Profile

We're going to get this added to the Known Issues, because it looks like we missed it, and as I said above, we're going to improve the default experience in VS so this isn't necessary :).

like image 147
Andrew Stanton-Nurse Avatar answered Sep 21 '22 12:09

Andrew Stanton-Nurse