Forum Discussion
How does "com4:ManagedInProcessServer" work under a MSIX packaging scenario?
I find the COM documentation difficult to turn into something useful as well. You first have to know how the COM object is built (meaning old-school terms), and then try to map them into this new registration method using different terms (which I'm sure meant something to someone, but isn't really shared in the documentation).
As a guess, the "Managed" version is related to "managed code" so if you were using regasm to register in the past, you should be in the right ballpark. When something like the ManagedInProcServer doesn't define the location of the dll, that means you also need another COM extension that maps the dll to something in the ManagedInProcServer element.
It might be you just need to combine both elements in the package (I think surrogate maps to in-process). But COM4:InProcessServer might be part of the answer as well.
Something that can help would be to download a copy of the Microsoft MSIX Packaging Tool from the Windows Store (free). Start it up to create a capture and run your regasm against the components. Stop the capture end go into the editor to look at the AppXManifest it generates. Then you'll know what you need.
Good luck. And after you figure it out feel free to feedback button on the bottom of the Documentation page to suggest improvements to the documentation!