Add Environment Variable to MSIX package using PSF Fixups in Packaging Tool - what am I missing?
Hi everyone, I am currently testing packaging apps into the MSIX format and have been successful for any simple installers. Now that I am trying to package more advanced installers I have to utilize PSF Fixups, in which I have issues with the Environment Fixup. Even though I have read up on previous discussions regarding this, I simply cannot get this fixup to be successfully added and recognized within the MSIX App. I am judging this based on that the same app will tell in its own app options whether the environment variable is available or not. Some key info (Tried attaching several screenshots, but it wilI not let me. Hopefully the necessary information comes across): Using MSIX Packaging Tool version 1.2024.405.0 Using the included PSF Fixup for Environment Variables within MSIX Packaging Tool. All PSF Fixup files are included in the MSIX Package. In the manifest file the executable "PsfLauncher64.exe" is pointed at. Basically, the config.json is formatted in the following way if I were to change out anything referring to the actual app name. What am I possibly missing out on or have misunderstood here? Any help in leading me into the right direction is very much appreciated, thanks!
MSIX Packaging Tool Command Line?
Has anyone succesfully used the MSIX Packaging Tool Command Line functionality? I haven't had any luck getting the packaging process to work with a template, and I can't find a single tutorial or post on the internet addressing it (besides the MS docs, which don't have any troubleshooting help). I see the create-package command has a verbose option, but I don't understand the error. Is there maybe event logs with additional info? Here's the verbose logging of my error: Running the installer About to start process - File name: %UserProfile%\Downloads\App\App Client Setup.exe - Arguments: /S /v/qn Received code 6 for job 2060 with value 13240 Installer still running Received code 7 for job 2060 with value 13240 Installer still running Received code 4 for job 2060 with value 0 App Client Setup.exe failed, exit code = -858993460 Restoring the environment Starting service. ServiceName : WSearch. Enabled Service : WSearch The conversion operation failed with: Process App Client Setup.exe failed with exit code -858993460. Stopping monitoring session Stopping the Monitoring session Stopping reboot listener Not really sure where to start with debugging this! I proved that I was able to run the installer directly from CMD using these same arguments and it installs fine.Unable to build APPXUPLOAD from .NET 9.0 / C# / WinForms project
Hi! We were advised by Microsoft Visual studio Developer community to create this issue on GitHub. But it was wrong direction. So, you're the third instance where we're trying to solve it. We hope that it is relevant to this section. Please, let us know if not. The corresponding threads can be found https://developercommunity.visualstudio.com/t/Unable-to-build-APPXUPLOAD-from-NET-90/10892325 and https://github.com/dotnet/winforms/issues/13377. --- The essence We’ve met this problem during the project (C#, WinForm) migration from .NET Framework 4.8.1 to .NET 9.0. Steps to see the problem We’ve migrated the project, compiled it and tested its functionality. Here we’ve found out that we are now required to publish the app with the .pubxml profile to make a single and not self-contained .exe instead of .exe-.dll-.json-.json… whatever this supposed to be. Using the publishing profile we’ve obtained the single-file executable that we’ve tested on Win10-x64 and Win7-x86. Both tests have been passed. The installation of .NET 9.0.4 desktop redistributables is not the problem for our aims. It is even better to not to “take” it with the executable. We’ve removed the .NET Framework project and added the .NET 9.0 project to the .wapproj dependencies without other changes. After this we get 3 warnings (fig. 1) about compatibility. After that we can get two results: The builder can create a 100Mb bundle for 450Kb executable or (if single file option is enabled) 100Mb the-entire-OS-in-one-file executable. So, we literally can build package. But it will completely ruin the user (who downloads the app from Microsoft Store) experience. Not to mention that such an installation size is simply inadequate for the goals and objectives of the product. With another project (we've tried it too) the builder can refuse to build the code during to non-existing errors (like missing ‘using’ directive). Exactly the same code has been successfully built during the publishing process 10 seconds ago. Our thoughts: there is some problem in the .wapproj file and/or in the MSIX builder. Because all warnings and errors come from the step before zipping .MSIXs into .appxbundle. --- How to reproduce directly Use this project to build a single-file-exe: https://github.com/user-attachments/files/19913854/TestProject_NET9.zip. This is the partial copy of our actual product without our own sensitive assemblies. It’s free for testing (available on GitHub). Add the new MSIX/APPX packaging project, connect the .NET 9.0 project to it. We can only provide our sample of .wapproj, without certificates and thumbprints, just to check its properties and verify its integrity: https://github.com/user-attachments/files/19913870/ScreenShooter_MSIX.zip. Try to publish the bundle. Tried workarounds Creating new .wapproj: no effect Clearing all building directories and caches: no effect Updating NuGets: no effect Other notes Also when builder tries to do its work we can see about 900 warnings about possible compatibility problems for basic methods from System, System.Windows.Forms and other assemblies. So, now we can still publish Android apps, APKs, Windows MSI packages, EXEs. But we cannot build apps for Microsoft Store. Which is not funny at all. --- So, how can we fix it? We’ve lost 6 hours in search. But found nothing useful. Thank you in advance, RD AAOW FDLPreview Handler with MSIX Packaging Tool?
Can anyone point me to a full example of an MSIX manifest file with a working preview handler for a custom file extension? I have developed a Windows exe and a dll preview handler for a custom file extension. I have a working Inno Setup installer that creates file associations for the file extension and assigns a preview handler so that the files can be previewed in Windows Explorer. I'm then using MSIX Packaging Tool to create an MSIX from the Inno exe installer. It mostly works and file associations are created correctly for the custom file extension. However, the preview handler doesn't work. Windows Explorer just shows 'Preview Unavailable' in the preview pane. I have found this topic, but it seems unresolved. Was this issue ever solved? Preview Handler in MSIX | Microsoft Community Hub From this I have found that entries may be missing from my manifest file for desktop2:DesktopPreviewHandler and com:SurrogateServer. However, I am new to MSIX and my efforts to add them in based on the documentation (link below) only results in an 'Unable to parse manifest' error from the MSIX Packaging Tool. The log file isn't much help showing only '[Error] System.Runtime.InteropServices.COMException'. https://learn.microsoft.com/en-us/uwp/schemas/appxpackage/uapmanifestschema/element-desktop2-desktoppreviewhandler Can anyone point me to a working example for a manifest file for a preview handler for a custom file extension, or a good tutorial? Here's my manifest file (with specifics renamed). <?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:uap2="http://schemas.microsoft.com/appx/manifest/uap/windows10/2" xmlns:uap3="http://schemas.microsoft.com/appx/manifest/uap/windows10/3" xmlns:uap10="http://schemas.microsoft.com/appx/manifest/uap/windows10/10" xmlns:desktop2="http://schemas.microsoft.com/appx/manifest/desktop/windows10/2" xmlns:desktop7="http://schemas.microsoft.com/appx/manifest/desktop/windows10/7" xmlns:rescap="http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities" IgnorableNamespaces="uap uap2 uap3 uap10 desktop7 rescap"> <!--Package created by MSIX Packaging Tool version: 1.2024.405.0--> <Identity Name="CompanyName.AppName" Publisher="---------------------------------------" Version="1.1.1.0" ProcessorArchitecture="x86" /> <Properties> <DisplayName>App Name</DisplayName> <PublisherDisplayName>Publisher Name</PublisherDisplayName> <Description>App Name</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" /> <PackageDependency Name="Microsoft.WindowsAppRuntime.1.4" MinVersion="4000.1010.1349.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" /> </Dependencies> <Applications> <Application Id="EXENAME" Executable="VFS\ProgramFilesX86\App_Name\AppName.exe" EntryPoint="Windows.FullTrustApplication"> <uap:VisualElements BackgroundColor="transparent" DisplayName="App_Name" Square150x150Logo="Assets\APPNAME-Square150x150Logo.png" Square44x44Logo="Assets\APPNAME-Square44x44Logo.png" Description="App Name"> <uap:DefaultTile Wide310x150Logo="Assets\APPNAME-Wide310x150Logo.png" Square310x310Logo="Assets\APPNAME-Square310x310Logo.png" Square71x71Logo="Assets\APPNAME-Square71x71Logo.png" /> </uap:VisualElements> <Extensions> <com:Extension Category="windows.comServer"> <com:ComServer> <com:SurrogateServer> <com:Class AppId="64644512-C345-469F-B5FB-EB351E20129D" SystemSurrogate="PreviewHost" /> </com:SurrogateServer> </com:ComServer> </com:Extension> <desktop7:Extension Category="windows.shortcut"> <desktop7:Shortcut File="[{Common Programs}]\App_Name\App_Name.lnk" Icon="[{Package}]\VFS\ProgramFilesX86\App_Name\AppName.exe" /> </desktop7:Extension> <uap3:Extension Category="windows.fileTypeAssociation"> <uap3:FileTypeAssociation Name="ext"> <uap:SupportedFileTypes> <uap:FileType>.ext</uap:FileType> </uap:SupportedFileTypes> <uap:Logo>Assets\ext.png</uap:Logo> <uap2:SupportedVerbs> <uap3:Verb Id="open" Parameters=""%1"">open</uap3:Verb> </uap2:SupportedVerbs> <desktop2:DesktopPreviewHandler Clsid="64644512-C345-469F-B5FB-EB351E20129D" desktop10:DisplayName="AppNameEXTPreviewHandler" /> </uap3:FileTypeAssociation> </uap3:Extension> </Extensions> </Application> </Applications> <Capabilities> <rescap:Capability Name="runFullTrust" /> </Capabilities> </Package>
MSIX Packaging tool fails to install offline for Win 11 22H2 and newer
Followed the instructions here: Using the MSIX Packaging Tool in a disconnected environment - MSIX | Microsoft Learn: dism /online /add-package /packagepath:"C:\MSIX\Msix-PackagingTool-Driver-Package~31bf3856ad364e35~amd64~~1.cab" but installation fails with error: Msix-PackagingTool-Driver-Package Error: 0x800f0818 CBS log provides the following detail: Info CBS Package doesn't match FOD for the current OS, package: Msix-PackagingTool-Driver-Package~31bf3856ad364e35~amd64~~10.0.22000.1, expected:Msix-PackagingTool-Driver-Package~31bf3856ad364e35~amd64~~10.0.22621.1 [HRESULT = 0x800f0818 - CBS_E_IDENTITY_MISMATCH]
MSIX package and shortcut icons
I see some strange behavior and can't explain why it is not working. I am playing around with the MSIX package and shortcut icons. I created them using the Visual Asset generator (https://apps.microsoft.com/detail/9mz6qrqtdkf2?hl=en-US&gl=US) and copied them to the Assets folder. When configuring the shortcuts with the files, the shortcuts and package logo stays blank. When I open the manifest and point the entries hardcoded to the files the icons appear. Like this config below. <Application Id="PSFLAUNCHERTwo" Executable="PsfLauncher2.exe" EntryPoint="Windows.FullTrustApplication"> <uap3:VisualElements AppListEntry="default" BackgroundColor="transparent" Description="Fair Prod" DisplayName="Fair Prod" Square150x150Logo="Assets\Edge-Square150x150Logo.scale-400.png" Square44x44Logo="Assets\Edge-Square44x44Logo.scale-400.png" VisualGroup="FCA"></uap3:VisualElements> </Application> But when removing the ".scale-400" part of the files, the icons would not appear. Anyone knows what I am doing wrong here?
Tips and Tricks Revealed on this Week's Friday Five!
First published on MSDN on Aug 31, 2018 Azure Key Vault recover keys, secrets and certificatesPeter Groenewegen has acquired extensive and varied experience as a Software Architect, Tech Lead, Consultant and Lead Developer, because of his work in development and service provision in a variety of organizations
