philip Castle

Author's posts

v24.5 Feature Release – HTML Email body Template Designer

New Feature Release – Please see release notes in Dashboard Update Utility Headlines: New Form Type Design Tab – HTML Editor for creation of HTML Email body templates, together with the amended script commands this allows the mapping of data directly into logic controlled templates to create HTML email bodies. Simplified Preview dialog option when …

Continue reading

Retiring: T3LPD Service

We have chosen to remove the optional LPD Server utility that is packaged with eVo after the release of the next release after Formate eVo 24.5 We are choosing to focus on where we can add value, and as the T3LPD service is not in common use we are removing it from the installation package …

Continue reading

Service Release 24.4 (24.4.25027.11122)

New Patch Release – Please see release notes in Dashboard Update Utility Headlines: Release corrects Bad Installer executable Signature. Release introduces new non solid line styles for layout line insertion and from scripting, with the new DrawLine2() script command

Oops – we got it wrong

We let eVo v24.4.24324.10907 out with a bad signature v24.4.24324.10907 was released with the Installer having a bad signature. This was unfortunate, but has no impact on the release, only the displayed signature. v24.4.24324.10907 is being withdrawn, and a new version released with a good signature, and another exciting change – one people have asked …

Continue reading

Formate eVo Task Despatcher Service Quarantined by AV Service.

Recently we have seen a couple of instances of updated AV software quarantining the eVo TD Service as a precaution. Obviously it is not a virus but some of the repetitive file access projects particularly around PDF editing and optimisation look awfully like it. We always state that the services, Program files, and Program Data …

Continue reading

2025 and the Future

Unusually Formate eVo v24 will continue for a few more months into 2025. This is to allow us to review the underlying .NET basis of eVo and evaluate the work needed to move from the classic .NET framework (4.8.xx) as used now to .NET v8 (Core). Alongside this we are going to take the chance …

Continue reading