undocumented COM element

%3CLINGO-SUB%20id%3D%22lingo-sub-1200750%22%20slang%3D%22en-US%22%3Eundocumented%20COM%20element%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1200750%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EHi%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3E%3CSPAN%3EUsing%20the%20MSIX%20Packaging%20Tool%20we%20get%20a%26nbsp%3B%3CSTRONG%3Ecom3%3AServiceServer%3C%2FSTRONG%3E%26nbsp%3Belement%20in%20our%20package%2C%20but%20we%20cannot%20find%20any%20docs%20on%20this%20element.%26nbsp%3B%3C%2FSPAN%3EIn%20the%20%3CSTRONG%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fuwp%2Fschemas%2Fappxpackage%2Fuapmanifestschema%2Felement-com-comserver%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EComServer%3C%2FA%3E%26nbsp%3B%3C%2FSTRONG%3Edocs%20we%20can%20only%20find%26nbsp%3B%3CSTRONG%3EExeServer%3C%2FSTRONG%3E%3CSPAN%3E%2C%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3ESurrogateServr%3C%2FSTRONG%3E%3CSPAN%3E%2C%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3EProgId%26nbsp%3B%3C%2FSTRONG%3E%3CSPAN%3Eor%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3ETreatAsClass.%26nbsp%3B%3C%2FSTRONG%3E%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3EAre%20there%20any%20docs%20updates%20in%20progress%20or%20....%3F%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3EThanks%2C%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3EBogdan%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1201666%22%20slang%3D%22en-US%22%3ERe%3A%20undocumented%20COM%20element%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1201666%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%3E%26nbsp%3BThat%20looks%20like%20a%20COM%2B%20entry.%20Run%26nbsp%3Bdcomcnfg.exe%20on%20the%20machine%20you%20installed%20it%20on%20and%20you%20should%20find%20something%20under%20there.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECOM%2B%20and%20DCOM%20were%20always%20things%20that%20App-V%20wouldn't%20support%2C%20so%20I%20wonder%20if%20this%20means%20MSIX%20may%20finally%20be%20supporting%20them%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1205127%22%20slang%3D%22en-US%22%3ERe%3A%20undocumented%20COM%20element%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1205127%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%3E%26nbsp%3BThis%20is%20part%20of%20the%20Windows%2010%202004%20release.%26nbsp%3B%20We%20are%20working%20on%20documentation%20updates%20for%20that%20release.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EJohn.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1206272%22%20slang%3D%22en-US%22%3ERe%3A%20undocumented%20COM%20element%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1206272%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%3E%26nbsp%3BI%20haven't%20tried%20poking%20around%20for%20AppX%2FMSIX%2C%20but%20the%20XSD%20schema%20for%20the%20App-V%20manifest%20could%20be%20obtained%20by%20extracting%26nbsp%3BAppVManifest.dll%20and%20AppVPolicy.dll%20via%207-Zip%20or%20a%20resource%20hacker.%20There%20may%20be%20a%20dll%20somewhere%20either%20from%20the%20OS%20and%2For%20the%20packaging%20tool%20that%20has%20an%20equivalent%20for%20MSIX...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1204731%22%20slang%3D%22en-US%22%3ERe%3A%20undocumented%20COM%20element%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1204731%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%2C%26nbsp%3Bour%20problem%20so%20far%20was%20not%20detecting%20what%20is%20installed%20on%20the%20machine%2C%20but%20how%20that%20resource%20should%20be%20defined%20in%20the%20AppXManifest%2C%20so%20that%20Advanced%20Installer%20can%20build%20a%20valid%20package.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe've%20done%20a%20lot%20of%20reverse%20engineering%20for%20our%20App-V%20support%2C%20hopefully%2C%20this%20will%20not%20be%20the%20case%20for%20MSIX%20too%2C%20and%20the%20MSIX%20team%20can%20point%20us%20towards%20the%20right%20docs.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Frequent Contributor

Hi,

 

Using the MSIX Packaging Tool we get a com3:ServiceServer element in our package, but we cannot find any docs on this element. In the ComServer docs we can only find ExeServerSurrogateServrProgId or TreatAsClass. 

 

Are there any docs updates in progress or ....?

 

Thanks,

Bogdan

 

 

4 Replies
Highlighted

@Bogdan Mitrache That looks like a COM+ entry. Run dcomcnfg.exe on the machine you installed it on and you should find something under there.

 

COM+ and DCOM were always things that App-V wouldn't support, so I wonder if this means MSIX may finally be supporting them?

Highlighted

Thanks @Dan Gough, our problem so far was not detecting what is installed on the machine, but how that resource should be defined in the AppXManifest, so that Advanced Installer can build a valid package.

 

We've done a lot of reverse engineering for our App-V support, hopefully, this will not be the case for MSIX too, and the MSIX team can point us towards the right docs.

Highlighted

@Bogdan Mitrache This is part of the Windows 10 2004 release.  We are working on documentation updates for that release.

 

John.

Highlighted

@Bogdan Mitrache I haven't tried poking around for AppX/MSIX, but the XSD schema for the App-V manifest could be obtained by extracting AppVManifest.dll and AppVPolicy.dll via 7-Zip or a resource hacker. There may be a dll somewhere either from the OS and/or the packaging tool that has an equivalent for MSIX...