CODEWITHSUNDEEP
.netgrpcgrpc-c#
JSchins
JSchins

Reputation: 117

gRPC ambiguous reference error when multiple packages share use of a Google CommonProtos type

We have a private nuget feed and our project is adding another gRPC service to consume from. After adding the second reference to the new gRPC service I get a build/compilation error due to both packages referencing Google.Type.LatLng in existing code that is creating a request object for the original gRPC service. It seems as if I can't specify which instance of Google.Type.LatLng to use. I added a reference to Google.Api.CommonProtos include a definition that may explicitly expose the Google.Type.LatLng but it seems like trying to prefix the LatLng with a namespace where it is being referenced (request.Location = new Google.Type.LatLong()) is not valid syntax.

I think I need to figure out what syntax or configuration will specify what declaration/package to use so I can compile without ambiguous reference errors, does anyone have experience with this issue?

Upvotes: 0

Views: 18

Answers (1)

JSchins
JSchins

Reputation: 117

It looks like I can add an alias to the package and reference it that way.

Upvotes: 0

Related Questions