-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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
Microsoft.AspNetCore.DataProtection.Abstractions higher version than referenced assembly #8527
Comments
Mixing package versions of Microsoft.AspNetCore.* is not supported. Looks like the "Main Project" is referencing DataProtection 2.2. That will need to be updated to 3.0 as well. |
Hi @Eilon , I could not find a 3.0 version, do i need to add a feed for this or is this something that will come at a later stage? Thanks |
Ah, you are right. That is one of the package that was moved into the ASP.NET "Shared framework." You can read more about that in the ASP.NET Core migration guide from 2.2 to 3.0: https://docs.microsoft.com/en-us/aspnet/core/migration/22-to-30?view=aspnetcore-2.2&tabs=visual-studio And there is some additional reference information here: |
Thanks! I'll take a look at this in a few hours. Appreciate the help. |
Fixed it with your help, now i reference Closing this as now it compiles and i can run the tests. |
Awesome! |
Describe the bug
Cannot write tests for IDataProtectionProvider because Visual Studio thinks I'm referencing a higher version in my main library. (The versions only go up to 2.2.0)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
That the compiler errors should just use the version the main library is using.
Unit Test Project
Main Project
Screenshots
Additional context
The .NET Core website runs perfectly fine. Including the DataProtector library, I've checked my database and it's encrypting the data. However, I have to comment out any class that uses this because the test project wont compile.
Include the output of
dotnet --info
The text was updated successfully, but these errors were encountered: