-
Notifications
You must be signed in to change notification settings - Fork 29.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VSCode/OmniSharp looking for DNX runtime in wrong directory #471
Comments
Provided symbolic link creates an additional folder under runtimes, so it still wasn't resolved. Correct (still hacky) symbolic link I believe is:
|
we adopted the latest version of omnisharp which should fix this |
@jrieken @egamma I still see the problem with 0.10.5. if you fully remove dnx from your machine ( If you follow the work around from stack overflow (ensure you set the default alias too) it starts to work again. |
Not a blocker for the Dec update, since there is a work around. |
I installed rc1 yesterday and the bit ended up in ~/.dnx. I will move this issue to OmniSharp because the lookup happens there. |
This issue was moved to OmniSharp/omnisharp-roslyn#369 |
On Mac OS, DNVM installed the DNX runtime in
/usr/local/lib/dnx/runtimes/dnx-mono.1.0.0-rc1-final
. However, OmniSharp in Visual Studio Code was incorrectly looking in/Users/danlo/.dnx/runtimes
. To get it to work properly, I created a symbolic link:This smells super hacky though.
The text was updated successfully, but these errors were encountered: