MSIX File Name Convention
- Last UpdatedApr 10, 2025
- 1 minute read
AVEVA has adopted the following convention for the naming of MSIX files.
Manufacturer.ProductName_ProductVersion.YYMM.ddhh.mmss_Platform__CertificateHASH.msix
|
Manufacturer |
= |
AVEVA |
||
|
ProductName |
= |
UnifiedEngineering |
||
|
ProductVersion |
= |
XXXX |
||
|
YY |
= |
two-digit Year |
||
|
MM* |
= |
two-digit Month |
||
|
dd* |
= |
two-digit day |
||
|
hh* |
= |
two-digit hour |
||
|
mm* |
= |
two-digit minute |
||
|
ss* |
= |
two-digit seconds |
||
|
Platform |
= |
AVEVA Unified Engineering is a 64-bit application this will therefore be x64. |
||
|
CertificateHASH |
= |
The certificate HASH is generated from the publisher details used to sign the MSIX package. |
||
|
In this case: |
||||
|
CN |
= |
AVEVA Group Limited |
||
|
OU |
= |
CAM-AVEVA-002 |
||
|
O |
= |
AVEVA Group Limited |
||
|
L |
= |
Cambridge |
||
|
C |
= |
GB |
||
|
The publisher details are parsed by a deterministic algorithm which, for this example, results with a certificate HASH of rmxc60bdg8z8w. |
||||
|
* Leading zeros are removed if they exist. |
||||
The naming convention enables all releases of AVEVA Unified Engineering.msix to be stored in the same directory without any file clashing file names.