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

Add support for multiple root folders #909

Open
DustinCampbell opened this issue Jul 13, 2017 · 12 comments
Open

Add support for multiple root folders #909

DustinCampbell opened this issue Jul 13, 2017 · 12 comments
Assignees

Comments

@DustinCampbell
Copy link
Contributor

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.

@DustinCampbell
Copy link
Contributor Author

For reference, here is the issue tracking the new API on the VS Code side: microsoft/vscode#28526.

@stewartadam
Copy link

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.

@mauve
Copy link

mauve commented Jan 25, 2021

Any idea when this will be addressed?

@filipw
Copy link
Member

filipw commented Jan 25, 2021

There are currently no definite plans.

@scgbear
Copy link

scgbear commented Feb 3, 2021

Internal Tracking devdivcsef 412378

@richardthombs
Copy link

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?

@GoaLitiuM
Copy link

This really needs to be fixed at some point...

@JeremyCaron
Copy link

Please.

@emouawad
Copy link

yup this needs fixing.. please

@CEbbinghaus
Copy link

+1

@JeremyCaron
Copy link

There are currently no definite plans.

Why not? Your process seems broken.

@leontev-vyacheslav
Copy link

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests