Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Change LdapSearchResults to IAsyncEnumerable
See original GitHub issueCan we drop support for .netstandard 1.3 in favor to use IAsyncEnumerable?
LdapSearchResults should inherit IAsyncEnumerable to use be full async. We can use await instead of .GetAwait().GetResult() in methods like GetEnumerator (–> GetEnumeratorAsync) or the inner Next (–> NextAsync)
IAsyncEnumerable will be supported in .netstandard >= 2.1 . So this will lead into another breaking change. For compatibility reasons we can install Microsoft.Bcl.AsyncInterfaces for .netstandard 2.0
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Everything is async now in 4.0.0. Closing this.
That functionality is like the original from 20 years ago and I just converted it to .net standard. I doubt that too many people will implement it like this these days. And I don’t think too many people are in fact using that functionality.
My thinking about this was to just remove that functionality in 4.0 and eventually offer something more raw and simple i.e. don’t assume how this is used by users. There is also an issue open about this - https://github.com/dsbenghe/Novell.Directory.Ldap.NETStandard/issues/152 - so a functional test needs to be added for this.