XYplorer Beta Club

I'm kind of surprised that you can't reproduce that. It happens every time for me. No, it's not a big deal, only annoying. Any kind of simple editing in the Edit dialog causes me to have to hit OK twice on the main Manage User-defined Commands dialog. I've disabled anything else like AHK that could potentially affect XY. Not a biggie though.

Ah yes, I see it now. The problem is that the focus goes astray after closing the Edit dialog. That's another one for Wayne.

admin wrote: ↑29 May 2025 16:59 Ah yes, I see it now. The problem is that the focus goes astray after closing the Edit dialog. That's another one for Wayne.

That makes sense, in that, if I click anywhere in the box then hit OK, it works. Thanks.

The dongle aka eToken from DigiCert finally arrived, 4 weeks too late. Okay, shit happens. But trouble does not end here. Look at the installation instructions from hell:
https://knowledge.digicert.com/solution ... ded-etoken

Right at the beginning it gets weird: I don't like this kind of nonsense. I contacted support (better safe than sorry — that dongle costs 1,500 euros), but I only received an automated response (AI). It was not helpful. They just rephrased my questions. I asked for a human. They promised me one. But will the human appear before the weekend? Sigh. Sorry, I'm bored.

PS: Why is this important here? Without a certificate I cannot publish anything. Not VB, not TB, not 32-bit, not 64-bit.

I've switched to "Microsoft Azure Trusted Signing" after my old certificate ran out

Setting it up in the first place is tricky but I got my certificate after about 30 minutes (which took me more than 3 weeks with the old certificate provider^^)
I don't need a hardware token (but i-net instead)
The thing does only cost 11,01 Euro / month
Quota: 5000 signings / month, above the limit 0,5 Cent per each

Maybe it's not for everyone but I like it

Thanks for the tip!

That was definitely my last gig with DigiCert. After 2 hours of working through a chaotic heap of docs it turns out the initialization code they created for me is "invalid, has already been used, or has expired". And no human support on weekends.

If I simply give DigiCert the boot and switch to Microsoft Azure Trusted Signing, how long would it take before I could sign my app again?

(By i-net you mean internet, right?)

i-net = internet, yeah

The only information I needed to supply iirc was an invoice (.pdf) for my domain (your domain + 2 e-mail addresses for it need to be supplied during the registration process anyway) and as I said, it took only 30 minutes to get the certificate.
The validation is through AI so in my case no human interaction was necessary and iirc I did it on a weekend

I followed this guide to the point to register everything: https://melatonin.dev/blog/code-signing ... d-signing/

To use it, you have to setup signtool afterwards...
Required packages:
https://dotnet.microsoft.com/en-us/download/dotnet/8.0
https://www.nuget.org/packages/Microsof ... BuildTools
https://www.nuget.org/packages/Microsof ... ing.Client

Did you look at that guide recently?

As of April 2025, Trusted Signing is restricted to US or Canadian businesses with more than 3 years history.

Hm.

No I didn't, I had mine registered several months ago

Seems you have to live with your current one until the general availability...

Pity. Thanks anyway!

In the meantime, a DigiCert support human approached me with a solution to my initialization code problem: I should reissue my certificate. The cost is 114 EUR. (Lacking a fitting icon to insert... )

Lack of icons hindered me to comment your "the hardware token did cost 1500 €"...

News from DigiCert:

The initialization code has expired because the order was approved on 2025-04-23. More than 30 days.

They are not even aware that the dongle arrived only on 2025-05-30 (their fault), and now they are asking me for an additional 114 EUR to make it work. What a disaster of an experience with the "leading provider of digital trust"!

Sorry, but I need to vent a little to feel better about my business practically coming to a halt because of DigiCert's incompetence.

And they don't change their mind about the fee when they are reminded that it took over 30 days to receive the necessary hardware? I'm glad that I don't have to deal with a certificate dealer that requires me to use a hardware token^^

Okay, now I made a mistake. I overlooked the “Use existing token” option, which allows you to request a new initialization code free of charge. Now I've requested a new code and am waiting again...