Skip to content
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

Closed
Daniel15 opened this issue Nov 23, 2015 · 6 comments
Closed

VSCode/OmniSharp looking for DNX runtime in wrong directory #471

Daniel15 opened this issue Nov 23, 2015 · 6 comments
Assignees
Milestone

Comments

@Daniel15
Copy link

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:

ln -s /usr/local/lib/dnx/runtimes /Users/danlo/.dnx/runtimes

This smells super hacky though.

@BenMagyar
Copy link

Provided symbolic link creates an additional folder under runtimes, so it still wasn't resolved. Correct (still hacky) symbolic link I believe is:

ln -s /usr/local/lib/dnx/runtimes/* /Users/<User>/.dnx/runtimes/   

@jrieken jrieken added the bug Issue identified by VS Code Team member as probable bug label Dec 9, 2015
@jrieken jrieken added this to the Dec 2015 milestone Dec 9, 2015
@jrieken jrieken added the c# label Dec 9, 2015
@jrieken
Copy link
Member

jrieken commented Dec 14, 2015

we adopted the latest version of omnisharp which should fix this

@jrieken jrieken closed this as completed Dec 14, 2015
@jrieken jrieken assigned chrisdias and unassigned jrieken Dec 16, 2015
@chrisdias
Copy link
Member

@jrieken @egamma I still see the problem with 0.10.5.

if you fully remove dnx from your machine (rm -rf ~/.dnx) and run setup from https://get.asp.net it will install the runtime globally into /usr/local/lib/dnx/runtimes. Create a new Web App using the aspnet generator, run dnu restore, and then open code on the folder.

If you follow the work around from stack overflow (ensure you set the default alias too) it starts to work again.

@chrisdias chrisdias reopened this Dec 18, 2015
@chrisdias chrisdias assigned jrieken and unassigned chrisdias Dec 18, 2015
@egamma egamma added the verification-found Issue verification failed label Dec 18, 2015
@egamma egamma modified the milestones: Jan 2016, Dec 2015 Dec 18, 2015
@egamma egamma added the important Issue identified as high-priority label Dec 18, 2015
@egamma
Copy link
Member

egamma commented Dec 18, 2015

Not a blocker for the Dec update, since there is a work around.

@jrieken
Copy link
Member

jrieken commented Dec 18, 2015

I installed rc1 yesterday and the bit ended up in ~/.dnx. I will move this issue to OmniSharp because the lookup happens there.

@jrieken jrieken removed bug Issue identified by VS Code Team member as probable bug c# important Issue identified as high-priority verification-found Issue verification failed labels Dec 18, 2015
@jrieken
Copy link
Member

jrieken commented Dec 18, 2015

This issue was moved to OmniSharp/omnisharp-roslyn#369

@jrieken jrieken closed this as completed Dec 18, 2015
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants