上一篇咱們提到了怎麼在Desktop Extension中等待並處理UWP端發出的request。本篇將討論UWP和Desktop Extension雙向交互的場景,即存在從兩端各自發出request,交由對方接受處理。
依然是回顧以前總結的四個場景分類:git
這種存在多個request/response週期的場景,具備如下特徵:github
該場景示意圖以下:async
上圖顯示了最簡化的雙向交互流程,在Sample工程中,以互相發文字消息的UWP和WPF窗體舉例。兩個窗體始終保持在前臺,也不存在AppServiceConnection被銷燬的問題。ide
而實際的業務場景中,可能存在複雜的變化。即特徵中提到的「Desktop Extension端知足條件時退出「這一點。函數
上圖爲Sample工程運行時的界面。如何使用Desktop Extension,及創建AppServiceConnection,以前的文章已解釋過,再也不說起。本篇僅對不一樣之處進行分析。
TwoWayExchange.FrontUWP是一個UWP工程,在MainPage.cs的構造函數中咱們經過AppServiceHandler這個幫助類來註冊Connected事件。this
public MainPage() { this.InitializeComponent(); if (ApiInformation.IsApiContractPresent("Windows.ApplicationModel.FullTrustAppContract", 1, 0)) { AppServiceHandler.Instance.Connected += Instance_Connected; FullTrustProcessLauncher.LaunchFullTrustProcessForCurrentAppAsync(); } }
該事件會在App.xaml.cs中的OnBackgroundActived方法中被觸發。這也是工程代碼中,實際和AppServiceConnection創建關聯的起點。spa
protected override void OnBackgroundActivated(BackgroundActivatedEventArgs args) { base.OnBackgroundActivated(args); if (args.TaskInstance.TriggerDetails is AppServiceTriggerDetails details) { if (details.CallerPackageFamilyName == Package.Current.Id.FamilyName) { var deferral = args.TaskInstance.GetDeferral(); args.TaskInstance.Canceled += (sender, e) => { deferral?.Complete(); }; AppServiceHandler.Instance.OnBackgroundActivated(details); } } }
在觸發Connected事件後,咱們在得到的AppServiceConnection對象上註冊RequestReceived事件,同時保存AppServiceConnection對象以供SendMessage時使用。3d
private void Instance_Connected(object sender, AppServiceConnectionConnectedEventArgs e) { AppServiceHandler.Instance.Connected -= Instance_Connected; Connection = e.Connection; Connection.RequestReceived += Connection_RequestReceived; } private async void Connection_RequestReceived(AppServiceConnection sender, AppServiceRequestReceivedEventArgs args) { var message = args.Request.Message; if (message.TryGetValue("Desktop", out object content)) { await Dispatcher.RunAsync(Windows.UI.Core.CoreDispatcherPriority.Normal, () => { this.textBoxReceive.Text += $"{content}\n"; }); } } private async void Button_Click(object sender, RoutedEventArgs e) { var valueSet = new ValueSet(); valueSet.Add("UWP", this.textBoxSend.Text); var response = await Connection.SendMessageAsync(valueSet); }
而在Desktop Extension的WPF工程中,幾乎是對稱的代碼結構,不一樣之處無非AppServiceConnection源頭是經過Desktop端的OpenAsync方法創建。code
public async Task InitializeAsync() { Connection = new AppServiceConnection(); Connection.PackageFamilyName = Package.Current.Id.FamilyName; Connection.AppServiceName = "TwoWayExchangeAppService"; AppServiceConnectionStatus status = await Connection.OpenAsync(); if (status == AppServiceConnectionStatus.Success) { Connection.RequestReceived += Connection_RequestReceived; } } private void Connection_RequestReceived(AppServiceConnection sender, AppServiceRequestReceivedEventArgs args) { if (args.Request.Message.TryGetValue("UWP", out object content)) { Dispatcher.Invoke(() => { this.textBoxReceive.Text += $"{content}\n"; }); } } private async void Button_Click(object sender, RoutedEventArgs e) { var message = new ValueSet(); message.Add("Desktop", this.textBoxSend.Text); await Connection.SendMessageAsync(message); }
至於打包用的Packaging工程,建立及注意事項,和前一篇徹底一致,再也不贅述。
本篇側重於雙向交互,在Desktop端注意Windows.mind和System.Runtime.WindowsRuntime兩個引用的添加,不然是沒法利用AppServiceConnection來通信的。
雖然文中示例極爲簡單,似沒有實用價值。而在實際開發中,多有遇到UWP端暫時沒法實現的UI及功能,諸如不規則的,透明的,或須要錨定的窗體,Windows桌面右下角的Systray等。都可以經過文中的方式來實現交互。
Github:
https://github.com/manupstairs/UWPSamples/tree/master/UWPSamples/DataExchangeUWP/TwoWayExchangeorm