Microsoft MSIX Packaging Tool and COM Capture issues leading to incorrect manifests

%3CLINGO-SUB%20id%3D%22lingo-sub-2061477%22%20slang%3D%22en-US%22%3EMicrosoft%20MSIX%20Packaging%20Tool%20and%20COM%20Capture%20issues%20leading%20to%20incorrect%20manifests%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2061477%22%20slang%3D%22en-US%22%3E%3CP%3EVersion%3A%20MMPT%202020.1219%3C%2FP%3E%0A%3CP%3EOS%3A%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%2020H2%3C%2FP%3E%0A%3CP%3EExample%20Application%3A%20MikTex%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECapturing%20MikTex%20leads%20to%20an%20inability%20to%20save%20the%20package.%26nbsp%3B%20This%20is%20traced%20down%20to%20a%20problem%20with%20the%20manifest%20which%20can%20be%20confirmed%20by%20using%20the%20package%20editor%20to%20edit%20the%20manifest%20and%20saving%20without%20change.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20most%20obvious%20issue%20is%20duplicate%20entries%20for%20many%20of%20the%20package%20level%20COM%20extension%20items.%26nbsp%3B%20In%20particular%2C%20com%3AProxyStub%20and%20com%3AInterface%20elements%20contain%20duplicates%20that%20violate%20the%20uniqueness%20rule%20for%20the%20Id%20parameters.%26nbsp%3B%20Manually%20cleaning%20out%20these%20duplicate%20entries%20leads%20to%20a%20valid%20manifest.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI'll%20attach%20an%20edited%20copy%20of%20the%20manifest%20where%20I%20have%20commented%20out%20all%20of%20the%20duplicates.%26nbsp%3B%20Note%20that%20there%20is%20an%20additional%20issue%20in%20the%20package%20whereas%20the%20MMPT%20detected%20app%20level%20com%3ASurrogateServer%20that%20it%20thought%20it%20should%20add%20but%20was%20unable%20to%20do%20so%20and%20just%20added%20it%20as%20a%20comment.%26nbsp%3B%20I%20did%20not%20add%20that%20comment%3B%20it%20came%20from%20the%20tool%20itself.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2062124%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20MSIX%20Packaging%20Tool%20and%20COM%20Capture%20issues%20leading%20to%20incorrect%20manifests%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2062124%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20for%20alerting%20us%20of%20this%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F146612%22%20target%3D%22_blank%22%3E%40TIMOTHY%20MANGAN%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20I%20understand%20this%20is%20the%20same%20issue%20you%20reported%20earlier%20in%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmsix-packaging-and-tools%2Fmsix-packaging-tool-failure-due-to-non-unique-com-proxystub%2Fm-p%2F2037465%22%20target%3D%22_self%22%3EMSIX%20Packaging%20Tool%20failure%20due%20to%20non-unique%20Com%3AProxyStub%20-%20Microsoft%20Tech%20Community%3C%2FA%3E%2C%20or%20am%20I%20missing%20something%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20is%20in%20our%20backlog%20and%20we%20will%20fix%20it%20for%20future%20releases%20of%20the%20tool.%20In%20the%20meantime%2C%26nbsp%3BI%20managed%20to%20reproduce%20the%20issue%20and%20I%20will%20let%20you%20know%20if%20I%20find%20any%20possible%20workaround%20to%20make%20the%20tool%20do%20the%20right%20thing%20without%20manually%20editing%20the%20manifest.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2063193%22%20slang%3D%22en-US%22%3ERE%3A%20Microsoft%20MSIX%20Packaging%20Tool%20and%20COM%20Capture%20issues%20leading%20to%20incorrect%20manifests%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2063193%22%20slang%3D%22en-US%22%3EYes%20it%20is.%20I%20finally%20got%20back%20to%20reproducing%2Fdocumenting%20issues%20I%20found%20during%20the%20holiday%20testing%20period.%20Didn't%20realize%20I%20already%20put%20it%20in.%20But%20at%20least%20now%20you%20can%20see%20what%20app%20is%20was%20to%20repo.%3C%2FLINGO-BODY%3E
MVP

Version: MMPT 2020.1219

OS:        20H2

Example Application: MikTex

 

Capturing MikTex leads to an inability to save the package.  This is traced down to a problem with the manifest which can be confirmed by using the package editor to edit the manifest and saving without change.

 

The most obvious issue is duplicate entries for many of the package level COM extension items.  In particular, com:ProxyStub and com:Interface elements contain duplicates that violate the uniqueness rule for the Id parameters.  Manually cleaning out these duplicate entries leads to a valid manifest.

 

I'll attach an edited copy of the manifest where I have commented out all of the duplicates.  Note that there is an additional issue in the package whereas the MMPT detected app level com:SurrogateServer that it thought it should add but was unable to do so and just added it as a comment.  I did not add that comment; it came from the tool itself.

 

2 Replies

Thank you for alerting us of this @TIMOTHY MANGAN ,

 

As I understand this is the same issue you reported earlier in MSIX Packaging Tool failure due to non-unique Com:ProxyStub - Microsoft Tech Community, or am I missing something?

 

This is in our backlog and we will fix it for future releases of the tool. In the meantime, I managed to reproduce the issue and I will let you know if I find any possible workaround to make the tool do the right thing without manually editing the manifest.

Yes it is. I finally got back to reproducing/documenting issues I found during the holiday testing period. Didn't realize I already put it in. But at least now you can see what app is was to repo.