-
Notifications
You must be signed in to change notification settings - Fork 473
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
ExpressionBinderBase issue with .NET 6 #2518
Comments
Hi @ysmoradi thanks for reporting this. Would you be willing to contribute a PR to fix this? We'd be happy to review your PR and support you in the process. |
@habbes I am hitting this issue attempting to update some projects to .NET 6. The problem I am having is that the newest NuGet package for this project does not support .NET Standard 2.0. We have a mixed codebase that consists of both .NET Framework and .NET Core projects and the code that is using the Microsoft.AspNetCore.OData package (and hitting this bug) is a .NET Standard 2.0 project that is shared by both .NET Framework and .NET Core projects. Is it possible to backport this fix to a version of the NuGet package that support .NET Standard 2.0? |
I just discovered that the 7.5.12 version of the package, which is .NET Standard compatible, appears to have this fix so I am unblocked. Thanks! |
This exception should occur in ASP.NET Core OData 8 too, because I'm talking about the code which exists in Shared section of repository codes
I've updated my owin / web api 2 project to .NET 6 and I'm getting a Sequence contains more than one matching element at following:
https://github.com/OData/WebApi/blob/master/src/Microsoft.AspNet.OData.Shared/Query/Expressions/ExpressionBinderBase.cs#L44-L45
Assemblies affected
OData WebApi lib 7.5.8
Reproduce steps
Run following in .NET 6 console app:
Expected result
TryParse method should get reflected.
Actual result
Invalid operation exception
Additional detail
In .NET 5 and older versions, we only have TryParse method which accepts a
string
value.In .NET 6, a new overload has been added which accepts
ReadOnlySpan<char>
The text was updated successfully, but these errors were encountered: