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 <https://chromium.googlesource.com/external/github.com/grpc/grpc/+/HEAD/src/csharp/BUILD-INTEGRATION.md>, 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 <https://github.com/grpc/grpc-dotnet/files/8375397/Grpc.zip> Thanks in advance if you have any ideas :) -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/e14553d9-fe3a-45a2-bd13-0384f9fcd8e0n%40googlegroups.com.
