-
Notifications
You must be signed in to change notification settings - Fork 420
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
Add support for multiple root folders #909
Comments
For reference, here is the issue tracking the new API on the VS Code side: microsoft/vscode#28526. |
Any progress on this front? On a moderately complex repo that has several sln files, it's annoying to have to open up each sub-folder in the file tree to get Omnisharp working correctly. |
Any idea when this will be addressed? |
There are currently no definite plans. |
Internal Trackingdevdivcsef 412378 |
Nearly 4 years on from when this issue was opened, is the advice in 2021 to structure folders so that you can open one vs code instance (and therefore one omnisharp instance) per solution? |
This really needs to be fixed at some point... |
Please. |
yup this needs fixing.. please |
+1 |
Why not? Your process seems broken. |
+1 |
Currently, OmniSharp requires a single root folder or solution to be specified at start up with the
-s
command line switch. Soon, VS Code will provide support for multiple root paths. To account for this, it should be possible to launch OmniSharp without setting-s
and then use end points to add and remove root paths that project systems would respond to.The text was updated successfully, but these errors were encountered: