Assembly file versions not set for Microsoft.AspNet.Identity.* 2.2.2

[davidkarlsson]

I'm wondering if there's a reason why the file version field for 2.2.2 hasn't been set for the Owin, EntityFramework and Core assemblies? For 2.2.1 the file version field was set to 2.2.1.40403 but in the latest version it's just set to 0.0.0.0.

This is causing us issues when we try to update the assemblies with a Windows Installer because it thinks that 2.2.2 is older than 2.2.1 since the file version fields are set to zero. So we are seeing errors like this for the Identity components:

MSI (c) (84:54) [16:21:44:440]: Disallowing installation of component: {49CB1C30-1258-4AB8-951C-D580FCAFD9F8} since the same component with higher versioned keyfile exists

I found this StackOverflow answer from Rob Mensching explaining the problem in greater detail: https://stackoverflow.com/a/15139855/253193

[JakeThurman]

I beleive this is the same issue, but our dependency scanner is flagging us for having 2.0.0 installed, because the AssemblyVersion is 2.0.0, and thus in our csproj file, it says:

<Reference Include="Microsoft.AspNet.Identity.Core, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL">
  <HintPath>..\packages\Microsoft.AspNet.Identity.Core.2.2.3\lib\net45\Microsoft.AspNet.Identity.Core.dll</HintPath>
</Reference>

The key part being the Version in the reference, even though it's clearly the 2.2.3 version anyway.

Also worth noting that wasn't manually configured, that's what gets setup from installing owin via nuget in visual studio 2019.