SOLVED

MS Word 2003 (or 2007, 2010)

%3CLINGO-SUB%20id%3D%22lingo-sub-1439666%22%20slang%3D%22en-US%22%3EMS%20Word%202003%20(or%202007%2C%202010)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1439666%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3CBR%20%2F%3EWe%20have%20not%20been%20able%20to%20compile%20a%20Word%202003%20package%20with%20the%20Advanced%20Installer%20for%20MSIX.%20Several%20COM%20objects%20have%20to%20be%20handled%20special%20and%20several%20registry%20entries%20have%20to%20be%20defined%20by%20hand.%3CBR%20%2F%3EIn%20addition%2C%20there%20is%20an%20extensive%20VBA%20application%20programmed%20in%20our%20house%2C%20which%20should%20also%20be%20in%20the%20package%20included.%20But%20I%20think%20the%20big%20stopper%20is%20already%20the%20plain%20Word%202003.%3CBR%20%2F%3EIf%20there%20is%20no%20chance%20to%20make%20it%20with%20Word%202003%2C%20Word%202010%20would%20also%20be%20an%20option.%20But%20all%20newer%20Word%20programs%20no%20longer%20support%20custom%20xml%20are%20not%20usable%20for%20our%20use%20case.%3C%2FP%3E%3CP%3EWe%20would%20also%20need%20a%20clean%20documentation%20for%20the%20procedure%20of%20MSIX%20creation%2C%20so%20we%20can%20compile%20a%20new%20MSIX%20app%20without%20external%20support%20in%20the%20future%2C%20when%20we%20make%20changes%20to%20our%20VBA%20code%20or%20new%20Word%20print%20templates.%3CBR%20%2F%3EI%20would%20also%20be%20willing%20to%20pay%20a%20reasonable%20amount%20for%20a%20solution.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1440174%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Word%202003%20(or%202007%2C%202010)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1440174%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%2F236102%22%20target%3D%22_blank%22%3E%40michael%20m%C3%BCller%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20package%20for%20Office%20applications%20is%20not%20something%20that%20can%20be%20automatically%20converted%20to%20MSIX%20or%20App-V%20(for%20that%20matter)%2C%20without%20any%20inside%20information%20about%20how%20it%20was%20built%20(information%20only%20available%20to%20the%20MS%20teams).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20recommendation%20is%20to%20way%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmsix-deployment%2Fmsix-packaging-of-office-applications-visio-project-proplus%2Fm-p%2F1058109%22%20target%3D%22_blank%22%3Euntil%20MS%20publishes%20its%20own%20version%20of%20an%20MSIX%20installer%20for%20Office%3C%2FA%3E.%26nbsp%3B%20This%20is%20what%20they%20did%20for%20App-V%20too%2C%20they%20had%20to%20make%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoft-desktop-optimization-pack%2Fappv-v5%2Fdeploying-microsoft-office-2016-by-using-app-v%23bkmk-create-office-pkg%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ea%20special%20build%3C%2FA%3E%20since%20their%20own%20App-V%20Sequencer%20couldn't%20simply%20repackage%20it%20successfully.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere%20is%20an%20excerpt%20from%20the%20last%20article%20linked%20above%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CBLOCKQUOTE%3E%3CSPAN%3EOffice%202016%20App-V%20Packages%20are%20created%20using%20the%20Office%20Deployment%20Tool%2C%20which%20generates%20an%20Office%202016%20App-V%20Package.%20The%20package%20cannot%20be%20created%20or%20modified%20through%20the%20App-V%20sequencer.%26nbsp%3B%3C%2FSPAN%3E%3C%2FBLOCKQUOTE%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-1442244%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Word%202003%20(or%202007%2C%202010)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1442244%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F147865%22%20target%3D%22_blank%22%3E%40Bogdan%20Mitrache%3C%2FA%3Ethank%20you%20for%20your%20information.%3C%2FP%3E%3CP%3EFor%20us%2C%20it%20would%20be%20important%2C%20that%20our%20lagacy%20Word%20will%20be%20suported%20als%20well.%3CBR%20%2F%3EIn%20what%20timeframe%20do%20you%20think%20it%20would%20be%20available%2C%20maybe%20there%20is%20already%20some%20kind%20of%20beta%20in%20the%20early%20adopter%20program%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMichael%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi,
We have not been able to compile a Word 2003 package with the Advanced Installer for MSIX. Several COM objects have to be handled special and several registry entries have to be defined by hand.
In addition, there is an extensive VBA application programmed in our house, which should also be in the package included. But I think the big stopper is already the plain Word 2003.
If there is no chance to make it with Word 2003, Word 2010 would also be an option. But all newer Word programs no longer support custom xml are not usable for our use case.

We would also need a clean documentation for the procedure of MSIX creation, so we can compile a new MSIX app without external support in the future, when we make changes to our VBA code or new Word print templates.
I would also be willing to pay a reasonable amount for a solution.

2 Replies
Best Response confirmed by Sharla Akers (Microsoft)
Solution

Hi @michael müller 

 

The package for Office applications is not something that can be automatically converted to MSIX or App-V (for that matter), without any inside information about how it was built (information only available to the MS teams).

 

My recommendation is to way until MS publishes its own version of an MSIX installer for Office.  This is what they did for App-V too, they had to make a special build since their own App-V Sequencer couldn't simply repackage it successfully.

 

Here is an excerpt from the last article linked above:

Office 2016 App-V Packages are created using the Office Deployment Tool, which generates an Office 2016 App-V Package. The package cannot be created or modified through the App-V sequencer. 

 

 

@Bogdan Mitrachethank you for your information.

For us, it would be important, that our lagacy Word will be suported als well.
In what timeframe do you think it would be available, maybe there is already some kind of beta in the early adopter program?

 

Michael