Release Date of Ix.Net v7

[emreyigit]

Hi everyone, I'd like to ask the planned release date for Ix.Net v7. If the info already has been presented but I couldn't find it, I apologize in advance. I'm providing async LINQ extensions over the Hazelcast .NET client, and due to reference ambiguity with Ix.Net v6 and .NET10, I have to offer a temporary fix for users who might use LINQ async. Based on the release date, I can do some forecasting for fix releases.

Many thanks in advance.

[idg10]

Sorry—the plan was to release it on the day .NET 10.0 GA'd but we did some last minute smoke tests that have revealed some problems.

We have released a preview. https://www.nuget.org/packages/System.Linq.Async/7.0.0-preview.10 is built for the .NET 10.0 GA build.

We need to run some more tests just to verify that this really does fix the issues we found. If we have no further problems, we will do a non-preview release early next week.

If it's possible for you to try this out to see if it works for you that would be great. (If it doesn't, then we can make sure the final version addresses whatever issues you encounter.)

[emreyigit]

Thank you for the reply.

[idg10]

We did find some more issues... We've just pushed out preview.14. I'm hopeful that we'll be able to to the proper release tomorrow.

[idg10]

This is now available at https://www.nuget.org/packages/System.Linq.Async/7.0.0

Thanks you for your patience.

We will be making a proper announcement soon, but this is now available for use.

Note that the long-term plan is to deprecate this package. Most of its functionality is now available in .NET 10's System.Linq.AsyncEnumerable (which is also available for use via NuGet on older versions of .NET). The features that Microsoft did not choose to replicate have moved into System.Interactive.Async. So System.Linq.Async now exists for backwards compatibility, but in the long run, libraries should look to stop using it.

[emreyigit]

Thank you @idg10 for the detailed explanation. We can handle the future changes. Main problem was clashes of two libraries on .NET10, and it's resolved with this release.