Renaming heserver

Pretty sure this request was on the old forum and lost when you guys went to this new one.

Need ability to rename the heserver to different names depending on the software app being built.

BTW: when will new verson of EXEOutPut be out that allows us to easily work with azure code signing?

The heserver hostname is hardcoded in the EXE's internal pluggable protocol (https://heserver/, http://heserver/, ghe://heserver/), and it is process-local, two ExeOutput apps running side by side on the same machine each have their own private heserver inside their own process, no collision. So today the value is purely cosmetic, it never leaks to the user unless they paste a link or peek at DevTools. It will be difficult to change this but it's on our TODO list again.

When does ExeOutput get easier Azure code signing?

Scheduled for ExeOutput for PHP 2026, which is the next major release. The integration mirrors what HTML Executable already ships today (https://www.htmlexe.com/help/topics/codesigning.html), the same UX with the Code Signing pane, the same SignTool + Dlib extension flow, the same Auto-probe for the Microsoft Artifact Signing Client Tools path. So when 2026 lands, your existing Azure Trusted Signing / Artifact Signing setup carries over directly, just point ExeOutput at the same SignTool + DLL paths you already use with XLS Padlock or HTMLEXE.

All good to know. When working with EXEOutOut and licensing servers, heserver name is important as it is always the same and hard to work with. But we are overcoming it by collecting the computer name and/or machine ID.

Ability to work with Azure code sign is a good thing, be glad to see it in new release.