Should not depend on MS.Bcl.Interfaces for .NET Core 3.0+ about featuremanagement-dotnet HOT 5 CLOSED

Hello @rjgotten, are you still experiencing this issue? It should be fixed by using the latest versions of nuget or dotnet restore when restoring packages.

For example, see this issue where it is discussed in further detail: Azure/azure-sdk-for-net#9632

from featuremanagement-dotnet.

@jimmyca15

I'm using dotnet core sdk 3.1.300 that comes with the latest VS 2019 and I'm still seeing this issue.
I need to have the mentioned alias in place or I'm still presented with error CS0121

The call is ambiguous between the following methods or properties:
'System.Linq.AsyncEnumerable.ToAsyncEnumerable<TSource> (System.Collections.Generic.IEnumerable<TSource>)' and
'System.Linq.AsyncEnumerable.ToAsyncEnumerable<TSource> (System.Collections.Generic.IEnumerable<TSource>)'

from featuremanagement-dotnet.

I'm not sure this is because of our dependency on the bcl package. I couldn't repro any issues by referencing it. Are you using System.Interactive.Async 3.2.0? That may be the cause.

I was able to reproduce the issue by running the console example project and adding a reference to System.Interactive.Async 3.2.0. There is a known issue with .NET core 3.x and System.Interactive.Async 3.x. Once I upgraded to System.Interactive.Async 4.1.1 it was resolved.

from featuremanagement-dotnet.

@jimmyca15
Went to have a look at the dependency tree for the affected project(s) again. We had one which was depending only on [email protected]. Switching it to take a dependency on the full [email protected] (and depend on System.Linq.Async transitively) indeed fixed the CS0121 error during builds.

(Very spooky that you actually must take a dependency on that external package for things to work correctly.)

from featuremanagement-dotnet.

Great sounds like this has been resolved then. Please raise another issue if anything feels off in the future. Thanks.

from featuremanagement-dotnet.