Vincent Parrett

There is no generic "works for everyone" main dpr setup for dunitx - the code depends on what logging and settings you want. You typically do not want the console logger or the xml logggers when using TestInsight - and when running on a CI server you probably don't want the console logger. I guess we could move some of the generated code to another generated unit so the IDE doesn't mess with the ifdefs - I don't have time to work on it at the moment but happy to accept a PR that improves this situation.

No, not specifically - you would just use signtool I guess. https://docs.aws.amazon.com/cloudhsm/latest/userguide/signtool.html However that seems to suggest this only works if you are running on an EC2 instance. I guess to use cloud hsm with signtool over the internet you would have to create vpn access (not sure if that is possible). FWIW, we are working on a product to simplify code signing with hsm's tokens (well ones that provide support pkcs#11). AWS does have pkcs#11 client library but we have not yet tested with it yet. I expect to make an announcement about the product in a few weeks (currently fleshing out the configuration interface).

On windows I just use hyper-v - on my macbook pro I use parallels - on my servers proxmox - no need for vmware at all.

Well that explains why don't miss it then, I don't do mobile dev.

Updating Indy will always cause problems with LivePreview - because Embarcadero created a dependency with Indy on that package. I never use the bundled version of Indy so I see this every time I upgrade - I just click No and move on (not sure what LivePreview does 🤷‍♂️)

that sent me down a rabbit hole for the last few hours 😉 The most interesting thing though was the link to talk on the Carbon compiler Super interesting talk (although annoying that he takes sooo many questions during the talk when we can't actually hear the questions and he doesn't repeat them - wish people would save the questions till the end). I've written bunch of lexers/parsers/ast's over the years - this talk makes me want to go and rewrite them all (of course I won't because I just don't have the time).

Yeah the filezilla download page is a bit disengeneous with that download button, it does however say (much smaller than the button) "This installer may include bundled offers. Check below for more options." which leads to this page https://filezilla-project.org/download.php?show_all=1 where you can download an installer that doesn't trigger windows defender or malwarebytes

Code signing doesn't guarantee that the file is virus free - it just proves that the file was signed with your (hopefully secured) certificate - ie the file came from who it said it comes from. As @Nigel Thomas said, your screenshot is of the timestamp certificate not the actual code signing certificate. Just for giggles I downloaded that file (in a dmz'd vm) and even windows defender doesn't like it. It's probably not a virus, just full of adware or potentually unwanted products. That said, I wouldn't actually install it.

Yes, and we did do that - but shared resources are aquired at the start of the stage (which means the token is in use for longer than it needs to be), so we had to split up our builds into more stages and that resulted in longer build times. I spent ages on various iterations trying different things. I found the virtualhere client would occasionally fail to disconnect the device and then builds would hang till I restarted the vh server. I guess it could be a latentcy issue, usb is very sensitive to it and our token and build servers are in different locations (300+ km). I will have a good solution to this available in a few weeks, working on a new product that makes sharing the tokens trivial (remote code signing server) and being able to code sign from any build agent.

I did experiment with that, but we ended up with build failures when multiple builds were running concurrently on different build agents.

Virtual here stays connected until you tell to disconnect or the link goes down. Virtualhere client also has an "auto use this device" option so it will always be available.

Correct - you need to disconnect using the virtualhere client and then connect on the other machine - it's a manual process.

because a usb device can only be used by one machine at a time. Virtualhere presents the device on the remote machine as though it were local.

I mentioned that it was discontinued since the OP mentioned that it was Free. We were long time hyper-v users here - but the cost of windows server licenses just to get a hypervisor were too expensive for us (from memory, it was around $6K per server, was a while ago so might be wrong) - we first switched to xcp-ng (a disaster) and more recently to proxmox (couldn't be happier). I put the money I didn't spend on windows licenses towards another server.

Embarcadero would need to move to a multi pass compiler to achieve this - something they have always resisted. I can understand this 10-15 yrs ago, but on modern hardware the compiler performance loss from multiple passes would not be that noticable. Edit : FWIW - in a multipass compiler, forward declarations are not usually needed (Java, C# for example don't use forward declarations).