Build break on Registry types

[AArnott]

I don't know how this is building in Azure Pipelines. The SignService is targeting netcoreapp3.1 but not referencing the Microsoft.Win32.Registry package. So local builds fail with this:

Utils\mansign2.cs(877,27): error CS0103: The name 'Registry' does not exist in the current context [D:\git\SignService\src\SignService\SignService.csproj] Utils\mansign2.cs(881,33): error CS0103: The name 'RegistryValueKind' does not exist in the current context [D:\git\SignService\src\SignService\SignService.csproj]
Utils\mansign2.cs(881,68): error CS0103: The name 'RegistryValueKind' does not exist in the current context [D:\git\SignService\src\SignService\SignService.csproj]

Is this really a configuration fail on my part somehow?

I'd like to send a PR that fixes the build break on my machine. I'd just feel better knowing how it works for anybody else.

[clairernovotny]

This is because of a bug in the 3.1.102 SDK. I just haven't put in the workaround for it; send you email offline.

[AArnott]

I stand corrected. It does fail in Azure Pipelines before my fix.