Updating dotnet from 7.0.102 to 7.0.203 causes user creation failure looking for a non-existent package

[dallas1287]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

When updating from dotnet 7.0.102 to 7.0.203 started getting this error when using the Identity.UserManager to create new users.
System.IO.FileNotFoundException: 'Could not load file or assembly 'Microsoft.AspNetCore.Cryptography.KeyDerivation, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'. The system cannot find the file specified.'

very similar to this issue #41368 but this was supposedly fixed in 6.0.4 but this occurs when going to the very latest in dotnet 7

Expected Behavior

No response

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

No response

Anything else?

No response

[Rick-Anderson]

Clear the NuGet package cache to ensure that you get the latest version of the packages.

dotnet nuget locals all --clear

What do dotnet --info and dotnet --list-sdks show?

try reinstalling the Microsoft.AspNetCore.Cryptography.KeyDerivation . Remove the package from your project and then add it again.

[dallas1287]

flushed my whole .nuget cache
dotnet --list-sdks reported 7.0.203 when the bug was happening, and 7.0.102 when i rolled back to visual studio 17.4.4
The package Microsoft.AspNetCore.Cryptography.KeyDerivation was never in my project, the exception was being thrown when the Identity UserManager was trying to create a new user

[mkArtakMSFT]

@wtgodbe is this something you're aware of?
@marcpopMSFT in case you've heard of similar behaviors after the recent release.

[wtgodbe]

I'm not sure why this would be the case - that library is part of our Shared Framework and is therefore shipped as part of the SDK. I just downloaded 7.0.203 and confirmed that it's in there, with a 7.0.0.0 AssemblyVersion

[mkArtakMSFT]

@dallas1287 can you share the deps.json file from the bin directory?

Hi @dallas1287. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

See our Issue Management Policies for more information.