UWP App communication with another process (*.exe)

DotNET Fan 211

UWP Experts,

We have a UWP app where we use a third party process (*.exe) and get the updates for file conversions.

We call the process using .NET Process class and get the conversion updates and based on the process exit code it is decided that the conversion is a success or not. Also we can cancel the conversion using the Cancellation Token.

This works well in the debug and release mode from Visual Studio. Unfortunately when it is installed from the windows store , it throws the exception

"An error in a system binary was detected.Try refreshing the PC to fix the problem".

We have tested in multiple systems and it shows the same issue.

Based on our initial investigation this is something to do with the permission as the UWP app is run in sandboxed env.

Is building a seperate fulltrust process configured through the package manifest an option here?
Is Named pipes in fulltrust process and UWP an option here? Are there any restrictions?
if we go with .net single contained process using Appserviceconnection class that communicates with the third party exe , it is limited as it can't work with .net5 or above and throws the build error.

Error NETSDK1130 Windows.WinMD cannot be referenced. Referencing a Windows Metadata component directly when targeting .NET 5 or higher is not supported.

What are the other good options here to communicate with the thirdparty process and get updates and cancellation?

Thanks

Roy Li - MSFT 33,371 Reputation points Microsoft Vendor

2024-10-04T06:32:25.6233333+00:00

I'm not sure how you use a third party process in your UWP app. Is it contained in your app or not?

Generally speaking, the recommended way is to create a desktop app like WPF, winforms, etc and package it together with your UWP app using WAPP. Do your work in the desktop app and then use app services to communicate between your UWP app and the desktop app. The UWP app will just need to show the result.
DotNET Fan 211 Reputation points

2024-10-04T06:56:06.2733333+00:00

@Roy Li - MSFT Yes it is contained in the app. The main app is UWP and the thirdparty process is not a WPF or winforms, but a win32 process (ffmpeg).

There are some limitations when using appservices in the desktop app as we cant use the windows runtime contract in .net 5 or above in the desktop app
Roy Li - MSFT 33,371 Reputation points Microsoft Vendor

2024-10-07T08:12:12.0433333+00:00

You could change the target framework of the desktop apps for example .net 6 desktop apps. to use runtime API. More information here: .NET 6 and later: Use the Target Framework Moniker option
DotNET Fan 211 Reputation points

2024-10-12T03:57:02.9066667+00:00

@Roy Li - MSFT , instead of using these complicated approaches , is there any other way to grant win32 process access through code or configuration and can be accessed through UWP like the way it is done when during development? During development i just added that in the assets folder and call it directky through process class which is quiet easy. But now with the full trust process i cant get it work as it always crashes the UWP app when the fulltrust process is called . Is it really require to package it during development also?
DotNET Fan 211 Reputation points

2024-10-14T13:35:00.6033333+00:00

@Roy Li - MSFT Adding to the above comment , is there any way to pass dynamic command line arguments to the trust process main method when calling through Windows.ApplicationModel.FullTrustProcessLauncher.LaunchFullTrustProcessForCurrentAppAsync() ? I see an overload which takes a string paramater , but it throws exception when we pass a string parameter - System.ArgumentException Parameter is incorrect
Roy Li - MSFT 33,371 Reputation points Microsoft Vendor

2024-10-15T02:23:33.0733333+00:00
Is it really require to package it during development also?

Yes.

is there any way to pass dynamic command line arguments to the trust process

The LaunchFullTrustProcessForCurrentAppAsync method could pass parameter to the process that you launched. But the parameter needs to be predefined in the manifest. The string parameter is the key to the parameter. A simple example is like this:

<desktop:Extension Category="windows.fullTrustProcess" Executable="Launcher\Launcher.exe"> <desktop:FullTrustProcess> <desktop:ParameterGroup GroupId="Background" Parameters="/background" /> </desktop:FullTrustProcess> </desktop:Extension>

To pass dynamic parameter, it's better to use appservice.
DotNET Fan 211 Reputation points

2024-10-15T05:29:53.2+00:00

You could change the target framework of the desktop apps for example .net 6 desktop apps. to use runtime API. More information here: .NET 6 and later: Use the Target Framework Moniker option

@Roy Li - MSFT

So this means we can build the fulltrust console app in .net 8 and target a specific runtime?

In UWP app we have a target version which is Windows 11, version 22H2 (10.0; Build 22621)

and min version - Windows 10 , version 1902 (10.0; Build 18362).

Considering the UWP target and min version , What is the version that we have to set for fulltrust console app targeting .net 8 with framework moniker option?
Roy Li - MSFT 33,371 Reputation points Microsoft Vendor

2024-10-15T06:59:33.93+00:00

Considering the UWP target and min version , What is the version that we have to set for fulltrust console app targeting .net 8 with framework moniker option?

This depends on your requirement. If you need a suggsetion, I would suggest use the same version as the UWP min version-18362.
DotNET Fan 211 Reputation points

2024-10-15T08:07:01.7466667+00:00

@Roy Li - MSFT

As per this link https://learn.microsoft.com/en-us/windows/apps/desktop/modernize/desktop-to-uwp-enhance#net-6-and-later-use-the-target-framework-moniker-option

it is mentioned to include net6.0-windows10.0.18362.0 for Windows 10 , version 1903 (10.0; Build 18362).

But what is the version of .net8.0 to include for Build 18362 ?

The document says

.NET 6 and later: Use the Target Framework Moniker option
DotNET Fan 211 Reputation points

2024-10-15T08:27:47.4633333+00:00

@Roy Li - MSFT As per the below link , for .NET 6 and later:

https://learn.microsoft.com/en-us/windows/apps/desktop/modernize/desktop-to-uwp-enhance#net-6-and-later-use-the-target-framework-moniker-option

Use the Target Framework Moniker option and include net6.0-windows10.0.18362.0 If your app targets Windows 10, version 1903 , Build 18362.

So what is version of .net 8.0 to include for windows 10 , version 1903 , Build 18362 ?
Roy Li - MSFT 33,371 Reputation points Microsoft Vendor

2024-10-15T08:40:03.6366667+00:00
Well, it's simple. The document already shows the format. You just need replace the 6 with 8 in the example code in your .net 8 app. Like

<TargetFramework>net8.0-windows10.0.18362.0</TargetFramework>
DotNET Fan 211 Reputation points

2024-10-15T08:56:52.83+00:00

@Roy Li - MSFT Thanks for the quick response.

Quick question , so UWP app will start multiple instances of fulltrust process each will start the Appservice server. How to differentiate Appservice service for Appservice connections started from UWP?
Roy Li - MSFT 33,371 Reputation points Microsoft Vendor

2024-10-15T09:18:38.53+00:00

Please keep one question in one thread. You could ask a new question on Microsoft Q&A about multiple instance related issue. Do you have any other concerns about the app communication?
DotNET Fan 211 Reputation points

2024-10-15T09:38:43.4333333+00:00

@Roy Li - MSFT Both are connected . For the UWP App , the appservice communication will be useful only if it supports the multiple instances scenario. That the reason for the question here.

I will create another question linking this case.
DotNET Fan 211 Reputation points

2024-10-15T10:26:07.48+00:00

@Roy Li - MSFT Please see the question raised for the multiple instances.

https://learn.microsoft.com/en-us/answers/questions/2103934/handling-appservice-connections-in-a-multiple-inst
DotNET Fan 211 Reputation points

2024-10-15T11:28:04.13+00:00

Please see the question raised for the multiple instances.

https://learn.microsoft.com/en-us/answers/questions/2103934/handling-appservice-connections-in-a-multiple-inst

Share via

UWP App communication with another process (*.exe)

Your answer