Forum Widgets
Latest Discussions
.WapProj build using "unvirtualizedResources" removed entry from manifest
I have a .wapproj that needs to use RegistryWriteVirtualization (aka "Flexible Virtualization) as described in Flexible virtualization - MSIX | Microsoft Learn This is for an MSIX package that will not be delivered via the Microsoft Store. The changes are made to the Package.appxmanifest file, and saved. The build action in Visual Studio removed the Capability declaration line for "unvirtualizedResources" from the Package.appxmaifest file before processing the file, leading to an error complaining that the RegistryWriteVirtualization requires this capability. Workaround: I can mark the file read-only outside of Visual Studio to keep VS from changing the file as a temporary workaround to prove out that the code depending upon these settings works. Why workaround is not acceptable: This workaround is not long-term viable, as other developers and automated workflows working on the project will lose the read-only setting (as it will not persist in GitHub) and have a broken build. It is clear that the VS code looking at this file is aware of both the desktop6 and virtualization schemas and their requirements and restrictions, but seemingly, although aware of other rescap capability extensions is unaware of this one. Requested action: Please add support for missing capabilities declarations in Visual Studio and/or underlying tools.MSIX .wapproj service
My agency is trying to move their services to MSIX/UWP and we found that the VisualStudio .wapproj .appxmanifest templates $targetnametoken$ and $targetentrypoint$ do not work for the properties 'Executable' and 'Entrypoint' of 'desktop6:Extension' tags with 'Category="windows.service"' despite working as expected on the enclosing 'Application' object. Can someone who knows how this is intended to work please help? I'm desperate at this point.VirtualizationManifestSchema needs correction
The version of the VirtualizationManifestSchema.xsd delivered as part of Visual Studio is still incorrect (I reported this about three years ago). It seems like the DesktopAppInstaller either ignores the regex pattern for the ST_ExcludedDirectory element or is using a fixed version for validation anyway. But other toolings depend on the accuracy of the published schema file for XML validation and it needs to be fixed. As stands, it looks like this: <xs:simpleType name="ST_ExcludedDirectory"> <xs:restriction base="t:ST_NonEmptyString"> <xs:pattern value="$\([kK][nN][oO][wW][nN][fF][oO][lL][dD][eE][rR]:[A-Za-z0-9]{1,32}\)(\\.+)?"/> </xs:restriction> </xs:simpleType> It should be: <xs:simpleType name="ST_ExcludedDirectory"> <xs:restriction base="t:ST_NonEmptyString"> <xs:pattern value="\$\([kK][nN][oO][wW][nN][fF][oO][lL][dD][eE][rR]:[A-Za-z0-9]{1,32}\)(\\.+)?"/> </xs:restriction> </xs:simpleType> This change would support the Syntax section shown in the documentation here: virtualization:ExcludedDirectory - Windows UWP applications | Microsoft Learn
Running windows service that's a part of a Desktop Bridge WFP app blocks update
I have a WPF application that has been packaged using DesktopBridge into MSIX and submitted to the Microsoft Store. This application has a WPF UI component, and it also has a windows service component that runs in the background whenever the PC is turned on. The UI component is used for configuring user settings and credentials for the windows service, and the windows service is actually the main component of this app. It's designed this way because of our client's needs. The problem that I'm running into is that when we publish a newer version to the Microsoft Store, the app fails to update with an error "0x80073D02: The package could not be installed because resources it modifies are currently in use" It looks like this is caused by the running windows service, and the store app update is not able to stop the service before the update replaces the files in the VFS. When the user manually stops the windows service, the update completes just fine and restarts the windows service as expected. When testing the update using different versions of MSIX files, I noticed that appending the flag -ForceApplicationShutdown to the Add-AppPackage command will achieve what I need, but this doesn't seem to be an option in the windows application packaging project, or in the Microsoft Store submission process. I know that including a windows service within an MSIX package is a restricted capability, so is this behavior due to the usage of this restricted capability? Also, is there a fix or workaround that will allow the update process to automatically stop the windows service before trying to replace the files? Thank you for any help or suggestions, and I'm happy to provide any additional information needed.
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.AppCompat with MSIX
Hi, I'm repackaging some (very) old apps in MSIX, and I'm facing a situation where I need to enable some app compatibility shims. I've tried doing this with the `registry.dat` registry hive, but it doesn't seem to work. I think I've heard something about using SDB in a MSIX package once, but I might be imagining things. Right now I've resorted to using an ImportRedirectionTable and a redirection DLL, but this only works for simple cases like Windows version lie. It would be amazing if there was a way to use an SDB inside a MSIX, but if the registry option could work, that'll do too. Did anybody manage to make this work? Thanks!
