Steve Wilford

Closing due to the underlying implementation changing to use templates where the constructor can be controlled.

@jariq hmm that won’t work for us, we need the signature to be attached to the original file as per Apple’s requirements: https://developer.apple.com/documentation/devicemanagement/configuring_multiple_devices_using_profiles#3234104 > To sign a profile, place the...

I tried the Pkcs11Interop.X509Store approach you linked earlier today but iirc the token I have doesn't have a certificate (it's currently 20:45 here so don't have the code to hand)

Here is the code and log output from the Pkcs11Interop.X509Store approach, no certificates are returned at all. ```csharp public static class HighLevel { public static byte[] Sign(byte[] dataToSign) { var...

Cool, I'll try and get round to having a look at this some time this week or next.

+1 for the label not found issue. ``` Error: "has conflicts" label not found in your repository! /home/autolabel/dist/lib/main.js:71 return label.node.id === conflictLabel.node.id; ```

I also get this issue when building for `netcoreapp3.1` and `net6.0` TFMs (the `netcoreapp3.1` build fails, while `net6.0` succeeds). >CSC : error CS1705: Assembly 'Be.Vlaanderen.Basisregisters.Generators.Guid.Deterministic' with identity 'Be.Vlaanderen.Basisregisters.Generators.Guid.Deterministic, Version=2.0.0.0, Culture=neutral,...

Digging into this a bit more I suspect that it's because the [.csproj file](https://github.com/Informatievlaanderen/deterministic-guid-generator/blob/main/src/Be.Vlaanderen.Basisregisters.Generators.Guid.Deterministic/Be.Vlaanderen.Basisregisters.Generators.Guid.Deterministic.csproj) gets all it's settings from https://github.com/Informatievlaanderen/build-pipeline/blob/main/generic/Be.Vlaanderen.Basisregisters.Build.Pipeline.Settings.Library.props which only specifies `net6.0` as the sole `TargetFramework`.

This didn't age well 😅 https://github.com/fluentassertions/fluentassertions/pull/2943

I don't think anyone did 😅