By dodgy_coder


2011-09-19 00:59:09 8 Comments

In a situation where you have the UI frontend built using the new Metro style of apps for windows 8, and would like it to communicate with a .NET application running on the desktop on the same local machine (e.g. a windows service app).

What forms of interprocess communication are available between the metro app and the desktop app?

Thanks to Pavel Minaev of the Visual Studio team, who has provided some initial info here in a comment, quoted:

According to Martyn Lovell, there isn't any deliberate mechanism for that, and some that could be used for it are intentionally restricted. Named pipes aren't there, for example, nor are memory mapped files. There are sockets (including server sockets), but when connecting to localhost, you can only connect to the same app. You could use normal files in one of the shared "known folders" (Documents, Pictures etc), but that is a fairly crude hack that necessitates polling and is visible to the user. -- Pavel Minaev commenting on this issue

So failing normal approaches I was thinking of using web services or reading/writing to a database in order to get some form of communication happening, both of which seem like overkill when the processes are running on the same machine.

Is what I'm attempting here making sense? I can see a need for a metro app to be the frontend UI for an existing service which is running on the desktop. Or is it better to just use WPF for the frontend UI running on the desktop (i.e. a non-metro app).

8 comments

@Wendelin 2015-10-25 12:18:41

Maybe I missed the point but when activating the Private networks capability I can connect to a local running (http) server using the local IP address (not localhost). This enables my scenario where a winrt app communicates with a wpf desktop app

@ig2r 2014-08-25 12:50:51

Take note that with Windows 8.1 Update, communication between Windows Store apps and desktop components written in C# for .NET 4.5+ is now officially supported for side-loaded applications in Enterprise scenarios:

Brokered Windows Runtime Components for side-loaded Windows Store apps

To quote:

Recognizing that critical business functions and rules are embodied in existing software assets and that enterprises have a wide variety of scenarios for which the new application style will be highly productive, the Windows 8.1 Update includes a new feature called Brokered Windows Runtime Components for side-loaded applications. We use the term IPC (inter-process communication) to describe the ability to run existing desktop software assets in one process (desktop component) while interacting with this code in a Windows Store app. This is a familiar model to enterprise developers as data base applications and applications utilizing NT Services in Windows share a similar multi-process architecture.

Although implementing this approach is a bit on the complicated side initially, it allows for deep integration across Windows Store and desktop components. Just keep in mind that for the time being, it won't pass public Windows Store certification.

@fgalliat 2013-08-02 22:10:51

If you think that you can make an additional manual cmd operation, you can try :

X:/> CheckNetIsolation.exe LoopbackExempt –a –n=<packageID>;

CheckNetIsolation.exe is included in winRT install, so there is nothing extra to be installed.

I tried it: it works, even after package updating.

As shown on: http://msdn.microsoft.com/en-us/library/windows/apps/Hh780593.aspx

Here it is explained how to find out the packageID for your app: http://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/82bad7d4-d52b-4731-a396-13ab9004c1cc/how-to-get-the-appid-of-a-metro-style-app-

@adosaiguas 2014-05-15 13:43:17

I wanted to be able to communicate with localhost for an internal application and I could only make it happen on the computers not running VS using this command.

@twj 2013-10-22 07:31:47

Christophe Nasarre has blogged about a rather hacky way to do it using local files. The result is communication between desktop app/windows store app (referred to as DA/WSA in the blog), without having to switch between the UI of the two apps. He also blogged about another less hacky technique involving protocol handlers.

Note that having a WSA which communicates with a DA is explicitly forbidden by the store App certification requirements

Windows Store apps must not communicate with local desktop applications or services via local mechanisms, including via files and registry keys.

... but it restricts "local mechanisms" only. So I guess one can build a web service for routing the communications.

@Martin Suchan 2012-10-01 17:02:38

It is possible to communicate on the same machine from Metro app to desktop app using local service. I've implemented some time ago simple "proof of concept", how to bypass the WinRT sandbox using local service. It still needs some kind of "social engineering" or direct guide for installing the service, but anyway, it is possible.
I'm not sure though about the certification rules about "local service" communication when adding such app to Windows Store.

Sample here

By design Metro application cannot access underlying PC directly, only using WinRT API and available capabilities. But when you create back-end service for accessing the PC and all data there, it's basically no longer running in sandbox.

The only "problem" is that user must manually install this back-end service, but that won't be a problem using some "social engineering": User downloads "PC browser" Metro app, user can browse all pictures, music and videos, using WinRT API, but the app also shows message at the bottom: "Download our PC browser powerpack and browse your entire PC, for FREE"

User is redirected to web page, from where user can download classic desktop installer containing "PC browser" back-end service for accessing files on users entire PC. Once this desktop service is installed, the Metro app can detect it and use it for browsing the entire PC. User is happy, but the WinRT sandbox is compromised.

Of course this won't work on Windows 8 ARM tablets. Using this workaround it could be even possible to build Metro app clients for classic desktop apps like antiviruses, torrent/P2P clients, etc.

@dodgy_coder 2012-10-02 02:29:41

Not sure why you need to mention about social engineering... since the original question is talking about a desktop app/service talking to a metro app, it is expected that the user will need to install the desktop app/service separately. So what method of communication did you use between the desktop service and the metro app?

@MuiBienCarlota 2013-09-17 14:42:17

It always works with Win 8.1 64 bits RTM.

@expert 2012-02-21 07:28:10

I'm porting my existing project to Win8 right now. It consists of windows service and tray application which are talking to each other via NamedPipes WCF. As you may already know Metro doesn't support named pipes. I ended up using TcpBinding for full duplex connection.

This post describes what functionality is supported.

Sample of my WCF server that Metro client can consume is here.

Also keep in mind that you can't use synchronous WCF in Metro. You'll have to use Task-based wrapper which is only asynchronous.

And thank you for you question. I was good starting point for me :)

@dodgy_coder 2012-02-22 00:53:20

Thanks for this ... that's a great help. Its good to see a practical answer instead of just being told that it shouldn't / can't be done.

@David Cuccia 2012-03-18 01:36:12

@dodgy_coder hear hear!

@dzendras 2012-08-21 08:02:41

It may be a stupid question... but you may connect to localhost using your sample or not? The question you link to shows the internals of Visual Studio (I deduced it from the path, but if I'm wrong, please correct me). Does WCF (combined with localhost) work outside of WCF?

@dzendras 2012-08-21 09:23:19

*outside of Visual Studio of course

@expert 2012-08-21 14:57:02

@dzendras What do you mean by "outside" ?

@dzendras 2012-08-21 16:36:42

when the app is run without VS's assistance (deployed)

@expert 2012-08-21 20:03:06

@dzendras Sure, it will work. It will work with localhost as well.

@Ani 2012-08-22 21:19:40

I doubt an app like this would pass Store certification, though.

@expert 2012-08-22 22:31:32

@ananthonline What part of license agreement does it violate?

@Ani 2012-08-23 15:44:54

If anything this is the rule I would think that might be quoted "3.9 All app logic must originate from, and reside in, your app package You app must not attempt to change or extend the packaged content through any form of dynamic inclusion of code or data that changes how the application interacts with the Windows Runtime, or behaves with regard to Store policy. It is not permissible, for example, to download a remote script and subsequently execute that script in the local context of your app package."

@ehdv 2013-06-25 23:59:31

This answer should include a caveat that it will very likely cause an application to fail Windows Store certification.

@expert 2013-06-26 15:59:51

@ehdv It's been a while now but as far as I remember Dell didn't have problems with certification.

@Hjulle 2013-11-28 08:15:46

@ananthonline As far as I understand none of the apps internal logic comes from an external source. This is just simple server-client software where both runs on the same computer.

@tronda 2011-09-21 08:41:47

There is an article on InfoQ about how to build loosely coupled Metro apps with protocol handlers. This is something which has been supported by Windows for a long time and one could foresee an desktop application register itself as a protocol handler and maybe the metro application can communicate through this mechanism.

I have no idea if this is possible, but it might be interesting to check out.

@Lumi 2011-12-05 19:48:04

The article says: "The way you can do this in Metro [jump over to another workflow in a different application - because your app is meant to be small and highly focussed] is by leveraging protocols. For our example above the protocol may look like “acme-stock-purchase://client=123&stock=XYZ”." - Just what does it mean technically, "leveraging protocols"?

@expert 2012-01-27 04:42:12

The problem with this approach is that it's only one way communication.

@Kate Gregory 2011-09-19 02:51:05

There were a number of questions like this at the end of a //build/ session I attended. Aleš Holeček, the exec who did one of the big picture sessions, came up out of the audience to handle them. Even if you're not a C++ developer, download that session and watch the Q & A. http://channel9.msdn.com/Events/BUILD/BUILD2011/TOOL-789C

Metro apps can't count on desktop apps or services being installed on the machine. And desktop apps can't count on Metro apps running since they can be suspended any time. You need to start thinking differently. Listen to Aleš on this one.

@Pavel Minaev 2011-09-19 03:01:02

This exact question seems to be asked at 47:20 in the video.

@Kate Gregory 2011-09-19 03:03:09

@Pavel, my point! Thanks for the time marker!

@Pavel Minaev 2011-09-19 03:08:30

... and one more at 55:00. The answer, generally, speaking, seems to be "nope you can't do that".

@dodgy_coder 2011-09-19 03:21:49

Thanks for the markers, yeah the speaker is saying that due to the strict sandboxing, its not really possible, but may be achieved by using the shared files workaround. Probably the best way then is to just assume they may not be on the same machine and use web services or WCF/tcp binding.

@Pavel Minaev 2011-09-19 03:34:18

@dodgy_coder I'm not sure WCF/TCP (or HTTP) would work on the same machine. If the sandbox doesn't let you connect to localhost directly via a TCP socket, why would it let you do the same via WCF?

@dodgy_coder 2011-09-19 04:06:17

@Pavel I was thinking of communicating via web services over a valid/live domain, not localhost... so in effect the comms go out to the internet (or intranet) and back.

@dodgy_coder 2011-09-28 03:07:05

Interestingly, there is built in support for communicating between two metro apps via share contracts but this seems to be similar in usage to the clipboard, and for transferring one-way from a source app to a target app, rather than for implementing say a two-way communication protocol.

@David Cuccia 2012-03-18 01:41:21

Seems to me that side-loaded LOB Metro apps would have no problem depending on an installed desktop app or service. I have a hard time believing this very practical scenario won't be supported. With Silverlight, we saw a gradual increase in desktop/native interop capabilities...I'm pretty sure something along these scenarios (named pipes, or memory-mapped files, or something...) will be supported (with guidance docs) in the future.

Related Questions

Sponsored Content

7 Answered Questions

[SOLVED] Is there a list of "standard" Tile colors for Metro style Windows 8 apps?

1 Answered Questions

1 Answered Questions

1 Answered Questions

1 Answered Questions

[SOLVED] Communication between desktop and metro app

1 Answered Questions

Sponsored Content