Closed mhDuke closed 3 years ago
I think it's the same issue as https://github.com/firebase/firebase-admin-dotnet/issues/207
as per microsoft documentation, adding square brackets around package version number should solve the issue. for example:
<PackageReference Include="Google.Api.Gax" Version="[2.7.0]" />
Our Gax dependency is due for an upgrade (see #251). I think the same PR should address this issue as well.
Also I wish there was a way in .NET to restrict a dependency to specific major version (like NPM does for Node.js). It seems this can be achieved by specifying versions as [2.0.0, 3.0.0)
(which means any 2.x.x version but not. 3.x.x).
See https://docs.microsoft.com/en-us/nuget/concepts/package-versioning#version-ranges
Google.Api.Gax.Rest 3.2.0
should solve the issue. And yes, this is exactly what you might go for [2.0.0, 3.0.0)
. inclusive minimum, and exclusive maximum. I learnt some good stuff today. thanks.
there is a conflict arises when I include both
FirebaseAdmin 1.17.1
andGoogle.Cloud.Firestore 2.2.0
packages.FirebaseAdmin 1.17.1
package has a dependency onGoogle.Api.Gax 2.7.0
.Google.Cloud.Firestore 2.2.0
package has a dependency onGoogle.Api.Gax 3.2.0
.When installing both packages side by side in one .Net project, the
FirebaseAdmin 1.17.1
automatically grabs the higher versionGoogle.Api.Gax 3.2.0
which causes compile errors. specifically because the use ofMicrosoft.Bcl.AsyncInterfaces
inGoogle.Api.Gax 3.2.0
while usingSystem.Interactive.Async
inGoogle.Api.Gax 2.7.0
I guess this issue belongs here because
FirebaseAdmin
is not restrictingGoogle.Api.Gax
dependency to version2.7.0