[Question] Visual Studio 2022 solution gRPC projects regeneration on each compilation without changes

70 views
Skip to first unread message

VRO

unread,
Mar 31, 2022, 7:33:03 PM3/31/22
to grpc.io

Hello,

I have an "abnormal" behavior between the protos & the up-to-date of Visual Studio and I would like to know if you had already met this thing. Before opening this ticket, I spent several hours searching on the internet but I didn't find anything conclusive.

I managed to reproduce the behavior in a simple application that I share below.

1/ I don't understand why at each compilation, without any change in the whole project, all assemblies containing protos are regenerated.

Is there a configuration to have? Is it a gRPC or Visual Studio Up-To-Date bug?
I tried to switch to Detailed MSBuild to see the Up-To-Date Check Verbose but strangely no information came up of why theses files are regenerated.
I expect that if there are no changes on the proto assembly, we do not regenerate this file

2/ I also have this message warning : Protobuf item 'gRPCClient/Protos/ProtoTest.proto' has the ProtoRoot metadata '..' which is not prefix to its path. Cannot compute relative path.
We set the Link & RootPath on our protos to be accessible from other assemblies but it puts out this warning message.
I tried to find the information here, but I didn't find/understand anything to fix this issue.

The application (possibly overkill, but this is to simulate multi-assembly):

  • gRPCApp: the client console application
  • gRPCClient: contains the client/server protos (maybe not the best assembly name)
  • gRPCServer: gRPC server
  • gRPCServerAssembly: contains the gRPC server method

Grpc.zip

Thanks in advance if you have any ideas :)

Jan Tattermusch

unread,
Apr 20, 2022, 7:20:10 AM4/20/22
to grpc.io
FTR this has now been filed as https://github.com/grpc/grpc/issues/29361.
Reply all
Reply to author
Forward
0 new messages