Renaming file or creating new file breaks omnisharp lookup

Environment data

dotnet --info output:

.NET Command Line Tools (2.1.4)

Product Information:
 Version:            2.1.4
 Commit SHA-1 hash:  5e8add2190

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

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.5
  Build    : 17373eb129b3b05aa18ece963f8795d65ef8ea54

VS Code version:

Version 1.20.1 (1.20.1)

C# Extension version:

1.14.0

Steps to reproduce

Create a file or rename a file and wait for Omnisharp to parse the file.

Expected behavior

VSCode should be able to find all existing namespace and assemblies.

Actual behavior

VSCode failed to find interfaces in the same namespace, and we can only reproduce it in current session, restarting VSCode, the issue is gone.

It seems Omnisharp somehow couldn’t recognize new file or renamed file are in the same namespace.

Screenshots

Existing file:

Create a new file with simple class name change:

Problems:

Restart or reload VSCode:

[Shnagenburg]

I’ve run into this problem as well with VSCode + Unity and would love a fix. I can only get it to consistently work by closing and restarting VSCode every time I create a new file.

[Blackclaws]

I have the same problem and I’m wondering why Omnisharp doesn’t simply add the file to a csproj that covers any file close by, this would at least work for creating files in the same directory as existing files.

Visual Studio is able to add files to an open Unity solution just fine. What is keeping omnisharp from doing the same? Or is this something that should happen on vscode project management level?