Is it even possible to get an in process .net COM library exposed from an installed MSIX package.  I have tried every combination of extensions (com4:ManagedInProcessServer came closest) and still can’t figure it out.  An application within the package doesn’t have any issue creating an object instance based on the COM class id so I know that my Registry.dat is correct but I can’t figure out the application manifest piece of the puzzle.  I want to be able to create instances of COM objects from outside the packaged application so that I can share logic between my applications.

If you have a working example of an app manifest can you reply?

Thanks.

​Is it even possible to get an in process .net COM library exposed from an installed MSIX package.  I have tried every combination of extensions (com4:ManagedInProcessServer came closest) and still can’t figure it out.  An application within the package doesn’t have any issue creating an object instance based on the COM class id so I know that my Registry.dat is correct but I can’t figure out the application manifest piece of the puzzle.  I want to be able to create instances of COM objects from outside the packaged application so that I can share logic between my applications. If you have a working example of an app manifest can you reply? Thanks.  Read More

​