In.Ex 4.0 preview NuGet build #14906
Comments
|
Pinging @divega to follow up on this one. |
|
@anton-beetroot-23071996 We're still working through the interaction of EF Core and the new async enumerable support in C# 8. We plan to have something to say publicly in the next few weeks, likely as part of a preview blog post. |
ajcvickers
added
the
closed-no-further-action
|
@ajcvickers Please take into account that this bug means that you cannot reference EF and Ix at the same time (direct or transitive). It's not only about support IAsyncEnumerable. |
|
@devsko This is a point-in-time situation. We plan to have a coherent solution before 3.0 ships. |
|
@ajcvickers Any update on this? |
|
@alan994 We working on it, but it's not quite ready yet. Hopefully it will make preview 6. More realistically, preview 7. |
|
@ajcvickers Hi) Is there exist any non-closed issue for this (or maybe PR), to track on its status ? |
|
@anton-beetroot-23071996 It will happen as part of #15498 |
|
@ajcvickers i'm still seeing this error on preview 8. |
|
@xaviergxf Please open a new issue and include a small, runnable project/solution or complete code listing that demonstrates the behavior you are seeing. |
|
I'm facing the same issue on preview8, @xaviergxf isn't alone. |
|
@shravan2x - As @ajcvickers said above, please open new issue with requested details so we can investigate. |
In.Ex team has recently released first preview NuGet package for In.Ex 4.0 with great API improovements, supports of new features and new async extentions (related PR - dotnet/reactive#423).
Currently I'm trying to use it in my project with EF Core, but due to type conflicts it causes TypeLoadException:
Message: System.TypeLoadException : Could not load type 'System.Collections.Generic.IAsyncEnumerable'1' from assembly 'System.Interactive.Async, Version=4.0.0.0, Culture=neutral, PublicKeyToken=94bc3704cddfc263'. .....It would be great to have EF Core updated with support of new version of System.Interactive.Async. Will it be possible ?
The text was updated successfully, but these errors were encountered: