Damon Tivel

This appears to be resolved by https://github.com/dotnet/sign/pull/758.

@sandy081, this is the important clue: ``` ManifestPackageIntegrityPolicy failed: unexpected package size. ``` The signature and manifest files look to be correct for the desired version. However, the VSIX file...

I see from the original post that this reproed on macOS. Is anyone experiencing the same issue on Linux or Windows?

https://github.com/dotnet/sign/issues/639 is the first step in solving this. After that, it would be up to whoever wants to implement a PKCS#11 signature provider for Sign CLI. I don't think there's...

@cpiock, are you intending to only sign one manifest (e.g.: deployment or application) or are you intending to sign a ClickOnce application (i.e.: _both_ deployment and application manifests)? If you're...

From your 👍, I assume this is now resolved.

@mjcheetham, I don't think this functionality belongs in Sign CLI. This feature ask should be on the Trusted Signing team, though I tend to agree with @joelverhagen that interacting with...

Hi, @MeikTranel. I don't see what you see. The README points to https://aka.ms/vs/17/release/vc_redist.x64.exe, which I obtained from https://learn.microsoft.com/cpp/windows/latest-supported-vc-redist?view=msvc-170#latest-microsoft-visual-c-redistributable-version I used these steps to download and verify the file: ``` curl...

@martincostello, can you try the latest version of Sign CLI just uploaded to NuGet.org? https://www.nuget.org/packages/sign/0.9.1-beta.24469.1 BTW, this is unrelated to the above issue, but your CI output includes the warning:...

As for ARM64EC, Sign CLI does use native interop, and according to [this](https://learn.microsoft.com/dotnet/standard/native-interop/abi-support#arm64ec), native interop isn't supported in ARM64EC.