Forum Discussion
MSIX -> Local Activation permission for COM
https://docs.microsoft.com/en-us/windows/msix/desktop/desktop-to-uwp-manual-conversion
Sigmarsson I am unable to help you further; you probably need to take this to a forum with more developers with similar experience. It sounds like you are pushing the edge to integrate old and new code into an MSIX package, and whether there is a procedural issue or (current) incompatibility I don't know.
I'm not sure that DCOM has anything to do with the issue; I'm guessing that it is a secondary issue. So going back to the beginning with code samples like this is more likely to help with someone more familiar with what you are attempting.
Hello Sir,
What exactly do you mean by old and new code, which I intend to push to the limits inside the MSIX box ?
This must be feasible somehow. There is a WPF splash attempts to launch another WPF both are based on the common TFM .NET 4.7. The first WPF ought to launch the second as a trusted process harnessing this MSIX package extension infrastructure. Pro boostrapper mechanism. If my take on is right.
I believe it is the right way to keep going what you prompted but either it is even now yet missing a puzzle or ... I do not know.
What discussion board do I ought to swing over ?
This ain't a pacage bundle, so what architecture is my package actually targeting ? I always compile Any CPU.
Is there a checklist I could go through to ensure compatibility ? Actually what you are suspecting.