question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

After Visual Studio 2017 Community RC dotnet stopped working

See original GitHub issue

Steps to reproduce

Installed update for VS 2017 RC

Expected behavior

dotnet ef [options] working

Actual behavior

It doesn’t work

Environment data

dotnet --info output: not working either

Windows 10 Pro 64-bits

dotnet --version:

Tracing enabled
--- Invoked dotnet [version: 1.1.0, commit hash: 928f77c4bc3f49d892459992fb6e1d5542cb5e86] main = {
dotnet
ef
}
Reading fx resolver directory=[C:\Program Files (x86)\dotnet\host\fxr]
Considering fxr version=[.]...
Considering fxr version=[..]...
Considering fxr version=[1.1.0]...
Detected latest fxr version=[C:\Program Files (x86)\dotnet\host\fxr\1.1.0]...
Resolved fxr [C:\Program Files (x86)\dotnet\host\fxr\1.1.0\hostfxr.dll]...
Loaded library from C:\Program Files (x86)\dotnet\host\fxr\1.1.0\hostfxr.dll
Tracing enabled
--- Invoked hostfxr [commit hash: 928f77c4bc3f49d892459992fb6e1d5542cb5e86] main
Own DLL path=[C:\Program Files (x86)\dotnet\dotnet.dll]
Checking if CoreCLR path exists=[C:\Program Files (x86)\dotnet\coreclr.dll]
--- Executing in muxer mode...
Detected a non-standalone application, expecting app.dll to execute.
Application 'ef' is not a managed executable.
--- Resolving dotnet from working dir
Probing path [C:\Users\...\Source\Repos\qurema\src\App\global.json] for global.json
Probing path [C:\Users\...\Source\Repos\qurema\src\global.json] for global.json
Probing path [C:\Users\...\Source\Repos\qurema\global.json] for global.json
Found global.json [C:\Users\...\Source\Repos\qurema\global.json]
--- Resolving CLI version from global json [C:\Users\...\Source\Repos\qurema\global.json]
CLI version is [1.0.0-preview3-004056] in global json file [C:\Users\...\Source\Repos\qurema\global.json]
CLI directory [C:\Program Files (x86)\dotnet\sdk\1.0.0-preview3-004056] from global.json doesn't exist
--- Resolving SDK version from SDK dir [C:\Program Files (x86)\dotnet\sdk]
No production version found, so using latest prerelease
Checking if resolved SDK dir [C:\Program Files (x86)\dotnet\sdk\-1.-1.-1] exists
Resolved SDK dir is []
Found CLI SDK in:
Did you mean to run dotnet SDK commands? Please install dotnet SDK from:
  http://go.microsoft.com/fwlink/?LinkID=798306&clcid=0x409

I’ve also tried to removeglobal.json (which exists soley for Azure, perhaps it is obsolete since Azure environment is now updated), but the same error still occurs

Error

Tracing enabled
--- Invoked dotnet [version: 1.1.0, commit hash: 928f77c4bc3f49d892459992fb6e1d5542cb5e86] main = {
dotnet
ef
}
Reading fx resolver directory=[C:\Program Files (x86)\dotnet\host\fxr]
Considering fxr version=[.]...
Considering fxr version=[..]...
Considering fxr version=[1.1.0]...
Detected latest fxr version=[C:\Program Files (x86)\dotnet\host\fxr\1.1.0]...
Resolved fxr [C:\Program Files (x86)\dotnet\host\fxr\1.1.0\hostfxr.dll]...
Loaded library from C:\Program Files (x86)\dotnet\host\fxr\1.1.0\hostfxr.dll
Tracing enabled
--- Invoked hostfxr [commit hash: 928f77c4bc3f49d892459992fb6e1d5542cb5e86] main
Own DLL path=[C:\Program Files (x86)\dotnet\dotnet.dll]
Checking if CoreCLR path exists=[C:\Program Files (x86)\dotnet\coreclr.dll]
--- Executing in muxer mode...
Detected a non-standalone application, expecting app.dll to execute.
Application 'ef' is not a managed executable.
--- Resolving dotnet from working dir
Probing path [C:\Users\...\Source\Repos\qurema\src\App\global.json] for global.json
Probing path [C:\Users\...\Source\Repos\qurema\src\global.json] for global.json
Probing path [C:\Users\...\Source\Repos\qurema\global.json] for global.json
Found global.json [C:\Users\..\Source\Repos\qurema\global.json]
--- Resolving CLI version from global json [C:\Users\...\Source\Repos\qurema\global.json]
CLI version is [1.0.0-preview3-004056] in global json file [C:\Users\...\Source\Repos\qurema\global.json]
CLI directory [C:\Program Files (x86)\dotnet\sdk\1.0.0-preview3-004056] from global.json doesn't exist
--- Resolving SDK version from SDK dir [C:\Program Files (x86)\dotnet\sdk]
No production version found, so using latest prerelease
Checking if resolved SDK dir [C:\Program Files (x86)\dotnet\sdk\-1.-1.-1] exists
Resolved SDK dir is []
Found CLI SDK in:
Did you mean to run dotnet SDK commands? Please install dotnet SDK from:
  http://go.microsoft.com/fwlink/?LinkID=798306&clcid=0x409

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:15 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
livarcocccommented, Dec 21, 2017

@lalalaring if you are referring to the core host trace, just set COREHOST_TRACE=0

1reaction
joacarcommented, Mar 15, 2017

@alexsandro-xpt This happens to me after every update. So fix the order of that paths in the environment variable and everything should start working

Read more comments on GitHub >

github_iconTop Results From Across the Web

Tests fail discovery, dotnet --version wrong after VS2017 ...
Tertiary problem is that it is not clear which version needs to remain installed to keep Visual Studio 2015 working and that there...
Read more >
Installing Visual Studio 2017 RC breaks dotnet core 1.0.1?
Build FAILED. Update: I have documented a workaround in the comments, but if there's a way to get both preview3 and preview2 tooling...
Read more >
Build fail after update to latest RC2/RC Refresh · Issue #482
When using Visual Studio 2017 (besides it crash a lot) it fail to build and multitarget is not working... To reproduce: dotnet new...
Read more >
Visual Studio 2017 Release Candidate
In Visual Studio 2017 RC you can directly work on code bases and files without any association with projects or solutions. Simply navigate...
Read more >
Visual Studio 2019 version 16.11 Release Notes
Note as well that versions 16.10 is no longer under support either. These intermediary releases received servicing fixes only until the next ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found