Is MSIX intended to support install of OS integration items?

%3CLINGO-SUB%20id%3D%22lingo-sub-1151715%22%20slang%3D%22en-US%22%3EIs%20MSIX%20intended%20to%20support%20install%20of%20OS%20integration%20items%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1151715%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22style-scope%20yt-formatted-string%22%3EIs%20MSIX%20intended%20to%20support%20install%20of%20OS%20integration%20items%2C%20like%20CredProv%2C%20NetworkProvider%2C%20VirtualChannel%2C%20shell%20extensions%2C%20property%20sheet%20handlers%3F%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22style-scope%20yt-formatted-string%22%3EAlso%20how%20about%20extensions%20for%20System%20Apps%20through%20MMC%20like%20ADUAC%3F%20ie.%20SOFTWARE%5CMicrosoft%5CMMC%5CSnapIns%20and%20Software%5CMicrosoft%5CMMC%5CNodeTypes%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1158367%22%20slang%3D%22en-US%22%3ERe%3A%20Is%20MSIX%20intended%20to%20support%20install%20of%20OS%20integration%20items%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1158367%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F319894%22%20target%3D%22_blank%22%3E%40GDomjan%3C%2FA%3E%26nbsp%3BI%20don't%20believe%20any%20of%20those%20are%20currently%20supported.%3CBR%20%2F%3E%3CBR%20%2F%3EApp-V%20supports%20shell%20extensions%20like%20property%20sheet%20handlers%2C%20and%20since%20the%20intention%20is%20to%20eventually%20replace%20App-V%20with%20MSIX%2C%20one%20would%20assume%20that%20they%20are%20on%20the%20roadmap.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EApp-V%20also%20lets%20you%20place%20the%20.msc%20files%20and%20dependencies%20in%20the%20package%20and%20create%20a%20shortcut%20that%20calls%20mmc.exe%20inside%20the%20container.%20I%20don't%20think%20MSIX%20support%20shortcuts%20to%20exes%20outside%20of%20the%20package%20yet%2C%20however%20it%20may%20be%20possible%20to%20fudge%20this%20by%20having%20a%20startup%20stub%20that%20calls%20the%20equivalent%20of%20the%20Invoke-CommandInDesktopPackage%20cmdlet.%3C%2FP%3E%3CP%3EFor%20those%20other%20items%2C%20I%20would%20doubt%20they'd%20make%20an%20appearance%20any%20time%20soon%20if%20ever.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1163287%22%20slang%3D%22en-US%22%3ERe%3A%20Is%20MSIX%20intended%20to%20support%20install%20of%20OS%20integration%20items%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1163287%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F145709%22%20target%3D%22_blank%22%3E%40Dan%20Gough%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20there%20are%20items%20the%20Desktop%20OS%20supports%2C%20yet%20are%20not%20supported%20by%20the%20MSIX%20installation%2C%20is%20there%20some%20suggested%20alternate%20packaging%20that%20should%20be%20used%20to%20be%20more%20compliant%20with%20Windows%20future%20requirements.%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20sticking%20with%20MSI%20and%20custom%20actions%20going%20to%20cut%20it%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1198280%22%20slang%3D%22en-US%22%3ERe%3A%20Is%20MSIX%20intended%20to%20support%20install%20of%20OS%20integration%20items%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1198280%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F319894%22%20target%3D%22_blank%22%3E%40GDomjan%3C%2FA%3E%26nbsp%3BRight%20now%2C%20MSI%20is%20pretty%20much%20your%20only%20option%20(and%20I'd%20stay%20away%20from%203rd%20party%20EXE%20builders%20like%20InnoSetup%20or%20NSIS%20if%20you%20can%2C%20enterprises%20like%20MSIs!).%20I%20don't%20think%20you%20have%20to%20worry%20about%20future%20support%20for%20MSI%20being%20taken%20away%20in%20the%20near%20future%2C%20for%20that%20would%20be%20commercial%20suicide.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1222106%22%20slang%3D%22en-US%22%3ERe%3A%20Is%20MSIX%20intended%20to%20support%20install%20of%20OS%20integration%20items%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1222106%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F319894%22%20target%3D%22_blank%22%3E%40GDomjan%3C%2FA%3E%20If%20there%20are%20things%20not%20supported%20by%20MSIX%20currently%2C%20it%20seems%20best%20to%20enter%20the%20information%20in%20the%20Feedback%20hub.%26nbsp%3B%20I%20also%20think%20it%20is%20a%20good%20idea%20to%20enter%20it%20in%20this%20venue%2C%20as%20the%20request%20is%20more%20public%20and%20there%20will%20be%20others%20interested.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Is MSIX intended to support install of OS integration items, like CredProv, NetworkProvider, VirtualChannel, shell extensions, property sheet handlers?

 

Also how about extensions for System Apps through MMC like ADUAC? ie. SOFTWARE\Microsoft\MMC\SnapIns and Software\Microsoft\MMC\NodeTypes

4 Replies

@GDomjan I don't believe any of those are currently supported.

App-V supports shell extensions like property sheet handlers, and since the intention is to eventually replace App-V with MSIX, one would assume that they are on the roadmap.


App-V also lets you place the .msc files and dependencies in the package and create a shortcut that calls mmc.exe inside the container. I don't think MSIX support shortcuts to exes outside of the package yet, however it may be possible to fudge this by having a startup stub that calls the equivalent of the Invoke-CommandInDesktopPackage cmdlet.

For those other items, I would doubt they'd make an appearance any time soon if ever.

Thanks @Dan Gough 

 

If there are items the Desktop OS supports, yet are not supported by the MSIX installation, is there some suggested alternate packaging that should be used to be more compliant with Windows future requirements. 

Is sticking with MSI and custom actions going to cut it?

@GDomjan Right now, MSI is pretty much your only option (and I'd stay away from 3rd party EXE builders like InnoSetup or NSIS if you can, enterprises like MSIs!). I don't think you have to worry about future support for MSI being taken away in the near future, for that would be commercial suicide.

@GDomjan If there are things not supported by MSIX currently, it seems best to enter the information in the Feedback hub.  I also think it is a good idea to enter it in this venue, as the request is more public and there will be others interested.