madorjan

Results 10 comments of madorjan

According to the license text, indirect usage of ImageSharp falls under the Apache 2.0 license. If I understand this correctly, for commercial Aardvark users that don't use ImageSharp directly, no...

OK, then I think an update to 2.1.7 would bei sufficient 👍

Tested this with version 0.0.556. It works when updating from velopack-install to velopack-install. Squirrel install overwrites always show the default repair dialog: [setup:23136] [09:38:26] [INFO] Reading bundle header... [setup:23136] [09:38:26]...

Another interesting library, however in development/experimental: https://github.com/iced-rs/iced ad slint: beware of licensing constraints due to GPL + commercial licensing model How can we contribute here? I think there must be...

fltk-rs sounds promising: latest release 2 weeks ago, only single exe, no additional dlls, image-support and themes. I'll fork your repo and try to implement a prototype UI. I'm new...

I have the same problem. "Trusted Signing" of a self-contained build always fails with: ![369873007-5a92a4b1-7c6a-49f7-9e86-ef0c94655dc4](https://github.com/user-attachments/assets/8129d6a2-bb11-4516-ae71-6cace8b2ea97) SDK 8.0.401 vpk 0.0.610 Signing with a locally installed certificate works, regardless of self-contained build...

Signing works with included signtool and following option: `--signParams "/fd SHA256 /tr http://timestamp.acs.microsoft.com /td SHA256 /dlib \"C:\Users\user\.nuget\packages\microsoft.trusted.signing.client\1.0.60\bin\x64\Azure.CodeSigning.Dlib.dll\" /dmdf \"absolute\path\to\signingInfo.json\""` Thanks for the workaround! So the problem was that the paths...

I implemented a `--azTrustedSign` parameter as suggested above. How should we distribute the CodeSigning.Dlib? Within the vendor folder like the signtool.exe?

You are right, unfortunately its not just a single DLL. Maybe we could access it using the https://www.nuget.org/packages/Microsoft.Trusted.Signing.Client package. I'll open a PR and we can discuss it there.

Thanks for continuing this pull request. Unfortunately, I haven't had time recently ... Any idea how to fix the signtool versioning issue in the long-term? Maybe, we have to download...