And yes I'm writing up a blog post, although I'm not sure if I'm going to be able to retrace my circuitous path of getting the final result. 😂. Pretty sure it'll be spicy 🔥🔥🔥.

So the CodeSign certificate has an expiration of. 3 days! So how does this work? Will it auto-renew every few days?. And if it does, isn't this going to wreak hell with Windows SmartScreen which notoriously resets its trust settings when the certificate is changed. @vcsjones

So I managed to get signing to work after a lot of back and forth and finally finding some actual documentation through many indirect links. But holy hell is it some ugly shit: .Install two separate SDKs ontop of the Azure SDK, reference a DLL explicitly

So I managed to get my Trusted Signing certificate set up. Now I'm trying to actually use it and I can't get anything to work. Anybody been through this? Do you need to use Azure Key Vault (seems no? There's no way to import the cert into it) and if not what actually works.

So after a bunch of searching that references resources no longer available because apparently the UI and naming has changed I end up on this lovely form:. Now you tell me what are you supposed to do here? You get to check checkboxes, but there's no Save or Apply or. maybe

As to the Azure UI: First thing is you have to enable a Role. No mention where to find that, where to set that up. I don't use Azure for shit (and this won't make me want to believe me!) so the error message is not helpful:

As it is the whole CodeSigning thing has turned into another scam of Enshittification of a captured audience. If you're publishing software or even packages on NuGet now, you pretty much have to have a certificate. Certificates that used to be ~$100-150 (or less for multi-year.

So I'm trying to check out Azure for Code Signing. This has to be the most insane UI train wreck I've ever seen. It's incredible how bad UI anything in Azure is in that it assumes you're intimately familiar with byzantine infrastructure of Azure Infrastructure and Microsoft.

Queuing the marketing phone calls in 3. 2. 1. (as soon as you log in to your account or run a license key).

FWIW, my WestWind.WebView library's HtmlToPdf generation will generate a Table of Contents, but it's based on the Html document's header structure that's built into the Chromium engine. It works off the headers in the document and walks them based on the h1, h2, h3 structure.

Ugh, finally managed to get an a working solution for my PDF generation of a custom topic tree that's not based on simple header structure. Ended up using SyncFusion's PDF tools which worked well to add the TOC to the generated PDF (via WebView export). Now to see whether their

And again this is one of those for me ever more common scenarios where LLMs completely went off the reservation hallucinating mostly non-functional code. I ended up wasting well over an hour with LLM generated code in Claude Code and GPT4.0 before just going back to my original.

I wonder though - perhaps what I'm seeing is just a limitation of the library I'm using? Anybody have any experience and feedback whether it's any easier to parse a PDF in a more structured way?.

The problem is that a PDF doc is not a structured document - it's just a bunch of text and shapes with formatting, so there's no easy way to look at things in terms of data. So I'm generating a TOC for a documentation project. Tree creation I can do. Collect the topics, specify.

The PDF format is such an incredibly fucked up document format. Spent all day today trying to get the built-in PDF TOC creation to work. Creating the TOC is easy enough but getting the links to go to the right page is ridiculously hard!

It's actually worse than that: it looks like if you don't specify the working directory, on ARM64 the path gets parsed as multiple parameters if there are spaces. That also doesn't happen on x64.

Ran into a few such things in the Markdown Monster logs where all the errors for this thing show up only on ARM64 systems.

Interesting: Finding that some shell operations are not working the same on ARM64 as they do on x64: Opening a folder with ShellExec fails on ARM but works fine on x64.

Blogged: Properly centering a WPF TreeViewItem in the TreeView ScrollViewer.

Personally I mostly use JetBrains @datagrip for most of my 'standard' database access, since it supports all sorts of data backends, but for some things SSMS still is easier to work with - creating DBs dealing with permissions, and other administrative tasks that I need once in a.