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

Omnisharp server startup is considerably longer after project.json to csproj conversion #1674

Closed
tetious opened this issue Jul 31, 2017 · 1 comment

Comments

@tetious
Copy link

tetious commented Jul 31, 2017

Environment data

dotnet --info output:
.NET Command Line Tools (1.0.4)

Product Information:
Version: 1.0.4
Commit SHA-1 hash: af1e6684fd

Runtime Environment:
OS Name: Mac OS X
OS Version: 10.12
OS Platform: Darwin
RID: osx.10.12-x64
Base Path: /usr/local/share/dotnet/sdk/1.0.4

VS Code version:
1.14.1
C# Extension version:
1.11.0

After converting my medium sized "solution" (11 total projects) from project.json to csproj, omnisharp server takes 40-50 seconds to start. (measured from opening a C# file in the editor until code-lens visibility)
Pre-conversion it took about 5 seconds.

I'm not sure what information I can add to help narrow this down. I'll help in any way I can. My guess though is that it might be related to the terrible dotnet build performance in the same scenario, due to the "upgraded" project system: https://github.com/dotnet/cli/issues/5918

@DustinCampbell
Copy link
Member

Yes, I'm looking at this performance issue right now actually. I'm using OmniSharp/omnisharp-roslyn#926 to track the work. You can follow that too.

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

2 participants