Implementing desktop extension for a multi instance uwp app

1

I followed this article to add desktop extension for my uwp app which is multi-instance. But I am getting deployment errors:

Deployment Error Prompt

Error DEP0700: Registration of the app failed. [0x80073CF6] AppxManifest.xml(79,10): error 0x80080204: Cannot register the package because EntryPoint must be specified when SupportsMultipleInstances is true.

If I provide entrypoint same as my uwp app(UWP.App in this case) although there is no deployment errors but the appserviceconnection fails with this message:

App not available

Any suggestion how I should go about this??

[Edit]

I made an out-proc AppService as described in this article and started it from full trust process following the same procedure in the article. But I can't seem to find any way to capture its instance from my uwp app. Any help??

uwp
windows-10
desktop-bridge
asked on Stack Overflow Apr 5, 2020 by SoumyaMahunt • edited Aug 29, 2020 by Stefan Wick MSFT

2 Answers

1

Create out-of-proc appservice as described here. Disable multi-instance for out-of-proc service. For each instance of uwp app create a new service. Create a static field in the background task class to store the appservice for desktop extension and initialize it when you create appservice from the desktop extension. Then you can pass messages from uwp app instances to out-of-proc appservice and then from appservice to desktop extension.

answered on Stack Overflow Apr 21, 2020 by SoumyaMahunt • edited Apr 21, 2020 by SoumyaMahunt
0

I am afraid the steps you are following are not applicable to multi-instance UWP apps, because in-proc AppService is not supported for multi-instance apps. This is documented here:
https://docs.microsoft.com/en-us/windows/uwp/launch-resume/multi-instance-uwp#background-tasks-and-multi-instancing

You can still launch a fulltrust process (desktop extension) from your multi-instance apps, but the cross-process communication as explained in the article you are following does not apply here. It's limited to standard, single-instance UWP applications.

answered on Stack Overflow Apr 7, 2020 by Stefan Wick MSFT

User contributions licensed under CC BY-SA 3.0