Forum Discussion
- Aniket_BanerjeeMicrosoft
You should certainly be able to see the version id. There are no changes, and I have verified this with the last few public releases. Can you confirm the version of MSIX Packaging Tool you are using?
Also, have you faced this issue more than once? We would like to get more information.
Yes. It happened on all 95 packages in last week's validation test. It isn't a big concern to me, but I am guessing that you didn't expect it. On the other hand, I didn't expect to see improvements in app compat that I saw in this version (based on the release notes) so kudos there!
Here is an example of the beginning of an AppXManifest file:
<?xml version="1.0" encoding="utf-8"?>
<Package xmlns="http://schemas.microsoft.com/appx/manifest/foundation/windows10" xmlns:uap="http://schemas.microsoft.com/appx/manifest/uap/windows10" xmlns:uap10="http://schemas.microsoft.com/appx/manifest/uap/windows10/10" xmlns:desktop6="http://schemas.microsoft.com/appx/manifest/desktop/windows10/6" xmlns:desktop7="http://schemas.microsoft.com/appx/manifest/desktop/windows10/7" xmlns:desktop9="http://schemas.microsoft.com/appx/manifest/desktop/windows10/9" xmlns:rescap="http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities" xmlns:com="http://schemas.microsoft.com/appx/manifest/com/windows10" IgnorableNamespaces="uap uap10 desktop6 desktop7 desktop9 rescap com">
<!--Package created by MSIX Packaging Tool version: -->
<Identity Name="AutoDesk-TrueView" Publisher="CN=TMurgent.local" Version="2024.0.0.0" ProcessorArchitecture="x64" />