Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Identity.UI produce assemblies that are built with implementation assemblies instead of reference assemblies. #18323
We discovered in 3.1.1 that Identity.UI assemblies. Specifically V3.dll and V4.dll. Combined with the bug described in #17970, runtime errors due to not being able to load the correct assemblies will be produced. Though we are fixing the related issue, we should ensure that the Identity.UI assemblies are built correctly.
The reason why Identity.UI specifically does not build correctly is because the customized logic at https://github.com/dotnet/aspnetcore/blob/release/3.1/src/Identity/UI/src/Microsoft.AspNetCore.Identity.UI.csproj#L59-L65 where MSBuild is launched to directly invoke the BuildForUI target. This bypasses the logic that we need to trigger at https://github.com/dotnet/aspnetcore/blob/release/3.1/eng/targets/ResolveReferences.targets#L249-L276.
My recommendation would be to try separating out the project into two new project for each of the V3 and V4 content and building them separately in the same way we build the other UI packages. Then compose the final Identity.UI package with the dll produced in the V3 and V4 projects.