Desktop Bridge – Multiple desktop processes, a single UWP container

Very informative article!

One thing that is still unclear for me is how one should deal with possible concurrent access to local settings by both a UWP part (e.g. a UI or a background task) and a win32 part in a Desktop Bridge app.

I have an app where a win32 executable (packaged inside the app) is launched by either the user through a UI or a periodically running background task. The UWP runtime will sometimes write some data in local settings and so does the win32 executable. The reason for letting the win32 process write to local settings instead of using the AppService connection is that the win32 process can take a long time to complete (it is a folder sync/backup app) and so the AppService connection would not remain active when it is launched by a periodic background task.

In 'normal' apps we protect shared access to a resource with a semaphore but that as far as I know would not help here.

Any suggestions on this?