Have you considered building Asp .net core identity yourself? I was trying to debug an issue in my applicaiton with my usermanager and it was calling some methods deep within the framework rather then trying to hop around the GitHub project I decided to try and build the library locally so that I could debug though it.
The source for Asp .Net core Identity can be found here on GitHub
Wont compile in Visual studio
The current .NET SDK does not support targeting .NET Core 2.1. Either target .NET Core 2.0 or lower, or use a version of the .NET SDK that supports .NET Core 2.1.
This is the first error I was getting the first thing you need to do is ensure that you are running the corect version of .net core sdk.
.NET Command Line Tools (2.1.2)
Commit SHA-1 hash: 5695315371
OS Name: Windows
OS Version: 10.0.15063
OS Platform: Windows
Base Path: C:\Program Files\dotnet\sdk\2.1.2\
Microsoft .NET Core Shared Framework Host
Version : 2.0.3
Build : a9190d4a75f4a982ae4b4fa8d1a24526566c69df
Now that we know I was running the corect version.
Command line build
Within the project is a build.cmd file that needs to be run to download all the files. Unfortunately this resulted in another error.
WARNING: dotnet found on the system PATH is ‘C:\Program Files\dotnet\dotnet.exe’ but KoreBuild will use
WARNING: Adding ‘C:\Users\lilaw\.dotnet\x64’ to system PATH permanently may be required for applications like Visual
Studio or VS Code to work correctly.
Fix windows path
By following the Building from source article we find that we need to change some things in windows default path. Basicly we need to remove C:\Program Files\dotnet from PATH in system variables and adding %USERPROFILE%\.dotnet\x64 to the user variables. Make sure you reboot after you have done this. Then run the build.cmd file again you should then be able to build the project within visual studio.
Not every developer wants to or needs to compile these frameworks locally. However as a developer its nice to know that if you need to you can and its really not that hard and not something you should be afraid of doing. I have been doing this for years I learn a lot by checking the source code in these projects a lot of the methods are not fully documented and you tend to find some nice surprises within the framework itself.