Build a MSIX package from the msi of an Excel vsto complement

%3CLINGO-SUB%20id%3D%22lingo-sub-824409%22%20slang%3D%22en-US%22%3EBuild%20a%20MSIX%20package%20from%20the%20msi%20of%20an%20Excel%20vsto%20complement%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-824409%22%20slang%3D%22en-US%22%3E%3CP%3EMSIX%20packaging%20tool%20does%20produce%20a%20msix%20package%20from%20the%20msi%20of%20an%20Excel%26nbsp%3B%20(2016)%20vsto%20complement%20but%20the%20built%20package%20doesn't%20seem%20to%20install%20properly%20neither%20appear%20in%20%22applications%20%26amp%3B%20functionalities%22%20menu.%3C%2FP%3E%3CP%3EAny%20light%20on%20this%20topic%3F%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-826989%22%20slang%3D%22en-US%22%3ERe%3A%20Build%20a%20MSIX%20package%20from%20the%20msi%20of%20an%20Excel%20vsto%20complement%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-826989%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F398946%22%20target%3D%22_blank%22%3E%40Raoul12%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20see%20you%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMSIX-Packaging-and-Tools%2FNo-Add-Remove-Entry-after-MSIX-package-installation%2Fm-p%2F824573%23M477%22%20target%3D%22_blank%22%3Eclarified%20where%20you%20can%20see%20the%20installed%20msix%20packaged%20apps%20and%20how%20you%20can%20uninstall%20them%3C%2FA%3E.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegarding%20extensions%2Fadd-ins%20that%20is%20a%20little%20bit%20complicated.%20First%2C%20the%20main%20app%20for%20which%20you%20deploy%20the%20extension%20should%20also%20be%20packaged%20as%20an%20MSIX%20package%2C%20otherwise%2C%20I%20don't%20see%20how%20the%20MSIX%20container%20of%20your%20add-in%20will%20interact%20with%20the%20main%20app.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThen%2C%20regarding%20how%20the%20OS%20handles%20the%20connection%20between%20the%20main%20app%20and%20its%20add-ins%20we%20suspect%20Microsoft%20will%20rely%20on%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fmsix%2Fpackage%2Foptional-packages-with-executable-code%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Eoptional%20packages%3C%2FA%3Esupport%20from%20MSIX%2C%20but%20we%20haven't%20seen%20any%20other%20announcements%20on%20this%20topic%20lately.%20Another%20%3CA%20href%3D%22https%3A%2F%2Fyoutu.be%2Fi26HOJZEvCo%3Ft%3D2472%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Eannouncement%2Fdemo%2Fpromise%3C%2FA%3Ewas%20demo-ed%20in%202018%20by%20MSFT.%3CBR%20%2F%3E%3CBR%20%2F%3EFrom%20my%20perspective%2C%20optional%20packages%20seem%20very%20similar%20with%20%3CA%20href%3D%22https%3A%2F%2Fyoutu.be%2Ff3Z7j1XEPgs%3Ft%3D222%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Emodification%20packages%3C%2FA%3E(I%20may%20be%20missing%20something)%20so%2C%20to%20be%20honest%2C%20I%20don't%20understand%20why%20the%20separation%20between.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-827636%22%20slang%3D%22en-US%22%3ERe%3A%20Build%20a%20MSIX%20package%20from%20the%20msi%20of%20an%20Excel%20vsto%20complement%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-827636%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20your%20remarks.%20Optional%20package%20seems%20interesting%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EI%20have%20been%20a%20little%20further%20on%20the%20topic.%3CBR%20%2F%3ENow%20the%20package%20installs%20properly%20on%20my%20computer%20and%20create%20a%20folder%20in%20programfiles%5Cwindowsapps%20includind%20a%20vsto%20file.%20If%20I%20copy%20the%20folder%20on%20my%20deksktop%20the%20addin%20installs.%20I%20doesn't%20work%20on%20another%20computer%20probably%20because%20of%20a%20certificate%20issue.%3CBR%20%2F%3EI%20am%20not%20sure%20how%20clean%20this%20approach%20is.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EUninstall%20issue%20was%20due%20to%20a%20corrupted%20initial%20project.%3CBR%20%2F%3E%3CBR%20%2F%3ERaoul%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

MSIX packaging tool does produce a msix package from the msi of an Excel  (2016) vsto complement but the built package doesn't seem to install properly neither appear in "applications & functionalities" menu.

Any light on this topic?

Thanks

2 Replies

Hi @Raoul12 

 

I see you clarified where you can see the installed msix packaged apps and how you can uninstall them.

 

Regarding extensions/add-ins that is a little bit complicated. First, the main app for which you deploy the extension should also be packaged as an MSIX package, otherwise, I don't see how the MSIX container of your add-in will interact with the main app.

 

Then, regarding how the OS handles the connection between the main app and its add-ins we suspect Microsoft will rely on the optional packages support from MSIX, but we haven't seen any other announcements on this topic lately. Another announcement/demo/promise was demo-ed in 2018 by MSFT.

From my perspective, optional packages seem very similar with modification packages (I may be missing something) so, to be honest, I don't understand why the separation between.

 

 

Thanks for your remarks. Optional package seems interesting


I have been a little further on the topic.
Now the package installs properly on my computer and create a folder in programfiles\windowsapps includind a vsto file. If I copy the folder on my deksktop the addin installs. I doesn't work on another computer probably because of a certificate issue.
I am not sure how clean this approach is.


Uninstall issue was due to a corrupted initial project.

Raoul