Forum Discussion
Naveen_Nooka
Microsoft
Oct 20, 2023MSIX Packaging tool - Insider Release now available
The latest version of the MSIX Packaging tool is now available in insiders. With features of Package Analyzer, PSF Fixup configurations from MSIX Packaging tool itself, this will simplify conversion process for applications into the MSIX (and App Attach ready format). Review the features and download the latest version of the tool - details mentioned at What’s new in MSIX: October 2023 | Windows IT Pro Blog (microsoft.com)
- martijnk79Brass ContributorAny idea how to download the insider release? I signed up but there's only a Windows store version. I need to install it to Windows Server 2019.
Thanks.- AppsPackGBrass ContributorIt would also be helpful for those using an offline environment to be able to obtain it outside of the store as part of the insider program.
- ravishroshan
Microsoft
martijnk79 Insider releases are only available via store. There will be a GA release in couple of weeks' time.
- martijnk79Brass ContributorFor some reason it's not available through Windows store as well. 807 seems to be the latest version. I did sign up for the insider program.
- atplsxBrass Contributor
Hi
It's great that you added these psf fixes. It does not run the package as administrator in the Packet Analyzer tab. That's why I can't analyze it.
<?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:rescap="http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities" IgnorableNamespaces="uap uap10 rescap"> <!--Package created by MSIX Packaging Tool version: 1.2023.1005.0--> <Identity Name="DismPlusPlus" Publisher="E=email address removed for privacy reasons, CN=Ottoman, OU=Ottoman, O=Ottoman, L=Istanbul, S=Turkiye, C=TR" Version="10.1.1002.0" ProcessorArchitecture="x64" /> <Properties> <DisplayName>Dism++</DisplayName> <PublisherDisplayName>Ottoman</PublisherDisplayName> <Description>Dism++</Description> <Logo>Assets\StoreLogo.png</Logo> <uap10:PackageIntegrity> <uap10:Content Enforcement="on" /> </uap10:PackageIntegrity> </Properties> <Resources> <Resource Language="en-us" /> </Resources> <Dependencies> <TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.17763.0" MaxVersionTested="10.0.22000.1" /> </Dependencies> <Applications> <Application Id="DSMXSixFour" Executable="VFS\AppVPackageDrive\Dism++\Dism++x64.exe" EntryPoint="Windows.FullTrustApplication"> <uap:VisualElements BackgroundColor="transparent" DisplayName="Dism++x64" Square150x150Logo="Assets\DSMXSixFour-Square150x150Logo.png" Square44x44Logo="Assets\DSMXSixFour-Square44x44Logo.png" Description="Dism++x64"> <uap:DefaultTile Wide310x150Logo="Assets\DSMXSixFour-Wide310x150Logo.png" Square310x310Logo="Assets\DSMXSixFour-Square310x310Logo.png" Square71x71Logo="Assets\DSMXSixFour-Square71x71Logo.png" /> </uap:VisualElements> </Application> </Applications> <Extensions> <uap10:Extension Category="windows.installedLocationVirtualization"> <uap10:InstalledLocationVirtualization> <uap10:UpdateActions AddedItems="keep" DeletedItems="reset" ModifiedItems="keep" /> </uap10:InstalledLocationVirtualization> </uap10:Extension> </Extensions> <Capabilities><Capability Name="internetClient" /><rescap:Capability Name="allowElevation" /><rescap:Capability Name="runFullTrust" /></Capabilities></Package>
Also, as I mentioned before, the starting point of portable programs is still not detected.
- Naveen_Nooka
Microsoft
atplsx - thanks for the input. In the preview version, analyzer tab doesn't work for apps that need elevated permissions. The item is in the backlog and we are looking to address this soon.
- martijnk79Brass Contributor
That's a very welcome update, thanks I will def. test this.
Btw, one more thing that annoys me is that I have to sign the package again with each version update with the certificate. Sometimes I have to make up to 20 version before my app works the way I want to so I need to sign it 20 times. is there not a more convenient way to accomplish this?- ravishroshan
Microsoft
martijnk79 You can save your signing certificate details in the settings page. With this the signing details will always be prefilled during all the flows.
- Naveen_Nooka
Microsoft
we strongly encourage packages to be signed for security reasons. But, during conversion if you have a need for repeated repackaging, you can create the package without signing and use command line to install the package - https://learn.microsoft.com/en-us/windows/msix/package/unsigned-package - Naveen_Nooka
Microsoft
martijnk79 - we strongly encourage packages to be signed for security reasons. But, during conversion if you have a need for repeated repackaging, you can create the package without signing and use command line to install the package. Create an unsigned MSIX package - MSIX | Microsoft Learn
- atplsxBrass ContributorI mentioned something else here, you are telling me about package signing. My packages are already signed