Changes in generated Proto types are not detected until nvim is restarted

[markvincze]

If I create a .NET project which has a <Protobuf> file reference, for example by scaffolding a gRPC service like this:

dotnet new grpc

Then open the solution folder with nvim, go to the greet.proto file, and do a change, for example rename the service Greeter to Greeter2. Then in a separate terminal I build the solution with dotnet build (which prints a build error as expected, because the type name in GreeterService.cs does not match the changed service name in the proto contracts.
But if I go back to nvim, and open GreeterService.cs, it does not yet show the build error. And the autocomplete is also still showing the old Greeter name.
If I restart nvim, then I get the build error being shown correctly, and the autocomplete shows the new type name.
(The change also gets detected if I don't restart nvim, but do :Roslyn restart.)

Has anyone encountered this issue before or knows how it could be fixed? In VsCode the same situation is handled correctly, the changes show up in the editor right away without needing to restart it.

(I believe that the types generated for the proto contracts are located in the obj folder of the project, in files with paths like obj/Debug/net9.0/Protos/GreetGrpc.cs.)

[markvincze]

I did not test this use case thoroughly yet, but for me the same thing seems to happen if I add a package dependency. So if on a separate terminal I do something like dotnet add package Newtonsoft.Json, then I need to restart nvim or do :Roslyn restart to make the new types appear.

[mkwpaul]

A much more convenient workaround to restarting nvim or restarting the language server is to just reload the buffer with :e!. (don't forget to write any pending changes to disk)

I don't know who exactly is responsible for invalidating stuff when it comes to langauges servers and LSP-clients, but either way it makes Roslyn re-analyze the file, as if you're opening a new buffer.

In my experience this also works with a bunch of other changes that the language server might not catch.
Like changing/removing/adding properties/items in the Project file. Or Generated code from other sources like WPF or tools like ResGen.exe or the Xsd utility.

So basically anything...

[byddha]

Related https://github.com/neovim/nvim-lspconfig/pull/4050/files#r2319114659

[seblyng]

Related https://github.com/neovim/nvim-lspconfig/pull/4050/files#r2319114659

I am not sure about that: #243

This is probably a filewatching issue