-
Notifications
You must be signed in to change notification settings - Fork 1.7k
IAuthenticationService.ImplementationType
returns Microsoft.AspNetCore.Authentication.AuthenticationServiceImpl
instead
#2262
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
Comments
I do not understand your request to the Ocelot team. Please send a short email message at [email protected] so we can continue the discussion. |
The issue is saying that if the tests are run having upgraded the code to .NET 10, then the test referenced in the issue will fail. If you changed the test as described, then you'll be in a good state for an upgrade after .NET 10 ships in November. |
@martincostello Hello, Martin!
However, Ocelot is currently completing the upgrade to .NET 9 only.
Understood. Thank you. We will keep this in mind. |
IAuthenticationService.ImplementationType
returns Microsoft.AspNetCore.Authentication.AuthenticationServiceImpl
instead
The same test code works in .NET 9 and .NET 10, so you could change it now and get it out of the way and forget about it. The one line change is already in the linked comment - I would have submitted a PR, but I don't know which of the two suggestions you want. |
When we run unittest Ocelot by command dotnet vstest with the latest version dotnet-sdk-10.0.100-preview.2.25125.6, it failed with error: The provided expression should be of type Microsoft.AspNetCore.Authentication.AuthenticationService but was Microsoft.AspNetCore.Authentication.AuthenticationServiceImpl.
After investigating, we found that this test failed due to the implementation was refactored in dotnet/aspnetcore#59557 to return a more derived type.
More detailed information about this issue, please refer to this comment:
dotnet/aspnetcore#60645 (comment)
The text was updated successfully, but these errors were encountered: