Why ASP.NET Core solution is falling after migrating to Visual Studio 2017?


I'm trying to migrate existing Web API solution to Visual Studio 2017.

It worked perfectly in Visual Studio 2015.

I followed automatic upgrade to VS 2017, but after starting solution with debugging it breaks and I get this error :

message:No script for id: 35
'dotnet.exe' (CoreCLR: DefaultDomain): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\1.0.4\System.Private.CoreLib.ni.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
The program '[6264] dotnet.exe' has exited with code -532462766 (0xe0434352).
The program '[14468] chrome.exe: WebKit' has exited with code -1 (0xffffffff).
The program '[5056] iisexpress.exe' has exited with code 0 (0x0).

After starting solution without debugging getting this error in browser.

It is not possible to debug solution at all. It breaks.

I can provide more informations, but right now don't know which are relevant.

EDIT: The solution consist of 3 projects. project.json and .csproj files of each project, as well as launchSettings.json are here. They reflect state after my dependencies consolidation.

Also, I can share the whole solution, so you can try to migrate by yourself.

asked on Stack Overflow Apr 13, 2017 by SFin • edited Apr 14, 2017 by SFin

2 Answers


The cause was bug in VS 2017 version 15.0 (26228.12). Upgraded to version 15.1 (26403.03) and error has gone.

answered on Stack Overflow Apr 14, 2017 by SFin

According @DOMZE result

try running it without IIS (where you have the start debugging button, click the little arrow and choose the name of your project, it will start KESTREL instead of hosting it in IIS) It's probably crashing because of a missing dependency

Secondly fallowing the @Alexan link to try all steps Migration from project.json to csproj . And doing the same thing what @Alexan mean that

try to clear the local nuget cache

After I tried those and couldn't fix the error. And I tried to following link to install core 2.0 sdk. And restart the visual studio 2017.

Here is the Link .net core 2.0 sdk

Note that if the link is gone you can find to google it to find ".net core 2.0 sdk".

answered on Stack Overflow Oct 22, 2017 by Emre • edited Oct 23, 2017 by Emre

User contributions licensed under CC BY-SA 3.0