-
Notifications
You must be signed in to change notification settings - Fork 679
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 not reloading references #4174
Comments
You are using version 1.23.4. 1.23.5 is even worse for me. It looks like new files are never added to the in memory workspace, while in previous releases new files were found most of the time after a little delay. @333fred could #4141 or #4143 have something to do with this? I am not running in a Docker context. |
Likely, I can reproduce it locally. I'll take a look. Thanks for the tag @tverboon. |
FWIW, I would very much expect .5 to be better than .4 here. I made a couple of bug fixes for .5, .4 will have very bad behavior if an external editor changes the file on disk. |
Yeah, sorry, I couldn't find the right words. It wasn't meant to say this complete version is worse, but I just started a new library project, so I am adding a lof of new files at the moment 😄 . I am following your work on Omnisharp and it's obvious you are really pushing this forward to give us a better experience. Thanks for that! |
A fix is available in this pre-release build - https://github.com/OmniSharp/omnisharp-vscode/releases/tag/v1.23.6-beta1. Instructions for installing our beta releases https://github.com/OmniSharp/omnisharp-vscode/wiki/Installing-Beta-Releases |
Here its not working yet... :( |
It sounds like the issue you're experience is unrelated Katekko. |
@333fred I'm still experiencing the same issue. Not sure if it's related to vscode-server (i'm working inside a docker container). Also I noticed that restarting omnisharp does not always fix the issue, but it seems that when that fails I can just reload the window and that will succeed in fixing the issue. |
We haven't released 1.23.6 yet. |
@333fred I can see it here https://github.com/OmniSharp/omnisharp-vscode/releases/tag/v.1.23.6 Am I missing something? |
@JoeRobich did we release this yet? I didn't think we did. |
@333fred We have. |
@gionapaolini then can you please open a new bug with repro instructions? |
Sure, I tried reproducing with a simple case using docker containers, but I wasn't able to reproduce. |
@ManfredLange can you try setting |
@333fred Thank you! I set From the OmniShar log:
As suggested I'll open a new issue. |
New issue filed: see #4223 |
Issue Description
Every time I reference a new class and get the quick fixes I don't get the option to add a "using namespace" statement to the file.
Also when I reference a new class contained in a namespace that is already referenced I still get the error:
The type or namespace name 'ClassName' could not be found (are you missing a using directive or an assembly reference?)
To fix it I have to manually restart Omnisharp
Some more context: I'm running VSCode on Docker containers
Steps to Reproduce
Expected Behavior
You should be able to get the option to add a Using statement when using the Quick Fix feature
Actual Behavior
Quick Fix feature not shown, unless Omnisharp is restarted
Logs
OmniSharp log
C# log
Environment information
VSCode version: 1.50.1
C# Extension: 1.23.4
Mono Information
OmniSharp using built-in monoDotnet Information
.NET Core SDK (reflecting any global.json): Version: 3.1.403 Commit: 9e895200cdRuntime Environment:
OS Name: debian
OS Version: 10
OS Platform: Linux
RID: debian.10-x64
Base Path: /usr/share/dotnet/sdk/3.1.403/
Host (useful for support):
Version: 3.1.9
Commit: 774fc3d6a9
.NET Core SDKs installed:
3.1.403 [/usr/share/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.App 3.1.9 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.1.9 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download
Visual Studio Code Extensions
The text was updated successfully, but these errors were encountered: