![]() $myPackAppVPackageDir - this is a variable inside my deployment Script that resolves to its current location Then you register the component by deployment (machine) script In the AppxManifest.xml assure to not have that ![]() Remove that Registry Class in the AppV-package I tested it due to an update to Version 8.6.1 ![]() Again, this is a solution for MSIX on Windows 11 as the extensions don't work on Windows 10. Both desktop4 and desktop5 schemas needed to be added at the top of the file as well. It is the desktop4:Extension element near the bottom. The adjusted AppXManifest file is attached in the image. Rather than turn the ignored shell extension into a Shell key, I modified the AppXManifest to support the shell extension. This, of course, only works on Windows 11. This support was added for MSIX in TMEditX 6.5, and has been coded in an unlreleased version of TMEdit for App-V at this time (it will be in v 3.7 of TMEdit when released).įor MSIX Packaing, the solution for the problem that I added focuses on supporting the skipped shell extension context menu handler. The fixes are based on supporting the ignored registration as shell extensions by manipulating the AppXManifest file. Approach to fix the problem by turning the shell extension into a traditional shell entry is something done in the native registry while in monitoring mode, so paths should look "normal".īut I did take a look this morning at the solutions that I added for this issues in my software.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |