Launch Local installed app in the context of MSIX package

%3CLINGO-SUB%20id%3D%22lingo-sub-1451724%22%20slang%3D%22en-US%22%3ELaunch%20Local%20installed%20app%20in%20the%20context%20of%20MSIX%20package%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1451724%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3ESo%2C%20when%20it%20comes%20to%20dependency%2C%20I%20see%20creating%20modification%20package%20is%20the%20only%20way%20to%20go%20about%20it%20and%20that%20too%20with%20limitation%20that%20the%20optional%20package%20should%20not%20have%20an%20entry%20point%20of%20its%20own.%20I%20believe%20there%20is%20always%20that%20option%20of%20capturing%20the%20main%20and%20dependent%20package%20as%20one%20single%20MSIX%20package%20(not%20very%20viable%20though)%3CBR%20%2F%3E%3CBR%20%2F%3EAnyways%2C%20do%20we%20have%20any%20functionality%20in%20place%20for%20MSIX%20package%20such%20that%20they%20can%20interact%20with%20a%20locally%20installed%20app.%20For%20Example%20the%20main%20package%20is%20locally%20installed%20and%20the%20dependent%20package%20is%20MSIX.%20On%20launching%20locally%20installed%20main%20package%2C%20the%20MSIX%20package%20is%20loaded%20in%20its%20context%2C%20something%20like%20RunVirtual%20in%20App-V%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1456615%22%20slang%3D%22en-US%22%3ERe%3A%20Launch%20Local%20installed%20app%20in%20the%20context%20of%20MSIX%20package%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1456615%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F680605%22%20target%3D%22_blank%22%3E%40DS2803%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere's%20a%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmsix%2Fmsix-runtime-support-debugging-using-external-launch%2Fidi-p%2F289497%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Elink%20to%20the%20full%20topic.%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETLDR%3B%20Use%3A%20the%20PS%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fappx%2Finvoke-commandindesktoppackage%3Fview%3Dwin10-ps%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EInvoke-CommandInDesktopPackage%3C%2FA%3E%3CSPAN%3E%26nbsp%3Bcmdlet.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hi,

So, when it comes to dependency, I see creating modification package is the only way to go about it and that too with limitation that the optional package should not have an entry point of its own. I believe there is always that option of capturing the main and dependent package as one single MSIX package (not very viable though)

Anyways, do we have any functionality in place for MSIX package such that they can interact with a locally installed app. For Example the main package is locally installed and the dependent package is MSIX. On launching locally installed main package, the MSIX package is loaded in its context, something like RunVirtual in App-V?

1 Reply
Highlighted