-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.NET Core 3 / .NET Standard 2.1 #46
Comments
@Numpsy, with the yesterday's official release of NET Core 3 and NET Standard 2.1 this library has been updated as well. Thanks for waiting! |
@kind-serge Does an implementation of |
@silkfire to my best knowledge |
On a sort of related note - Microsoft have released a Microsoft.Bcl.AsyncInterfaces package that has definitions of IAsyncEnumerable and such for versions of .NET prior to Standard 2.1. Any thoughts on using ParallellForEachAsync with those definitions? |
@Numpsy , thanks for the info! I was not aware of that package. |
@Numpsy , the new version has been released: https://www.nuget.org/packages/AsyncEnumerator/4.0.0 |
Thanks, I'll give it a go. |
I tried it in a .Net Standard 2.0 library called from a .Net 4.7.2 application and hit some errors about missing methods, i'm guessing because the library is using the interface definitions from the Microsoft package, but the build for the app is pulling in the .Net 4.5 build of AsyncEnumerator that doesn't contain matching methods? |
Seems like a .NET Fx 4.6.1 (and higher) project uses the .NET Fx 4.5 version of the library instead of .NET Std 2.0. I updated the NuGet Package with the .NET Fx 4.6.1 version of this library to be compatible with .NET Std 2.0 projects: https://www.nuget.org/packages/AsyncEnumerator/4.0.1 |
Thanks, that seems ok now. |
Hi,
I see that the most recent version of the library has been adapted to use the built in IAsyncEnumerable in .NET Core 3, but can I ask what the situation is with .NET Standard 2.1? (from a quick test, looks like it uses its own definition there rather than the built in version?).
Thanks.
The text was updated successfully, but these errors were encountered: