• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>
            隨筆 - 55  文章 - 15  trackbacks - 0
            <2012年9月>
            2627282930311
            2345678
            9101112131415
            16171819202122
            23242526272829
            30123456

            常用鏈接

            留言簿

            隨筆分類

            隨筆檔案

            搜索

            •  

            最新評論

            閱讀排行榜

            評論排行榜

               WCF相關知識我也不是很懂,只不過有任務要研究一下。主要目地還是Metro做UI,同Desktop App進行交互,想法是Metro做客戶端,Desktop做服務端。現在的情況是,client端的代碼可以移植到Metro下,但是server端不可以。所以我的理解是,只能單向通信了。那么,MSDN論壇上也在問,如果有一個用戶想做主機,其他用戶連進來,不能用WCF怎么辦?
            微軟的答復是:用Socket,或者用云,大家都鏈接到云,跟用戶的設備無關。這不是紅果果地推銷Azure么。
               下面是我的研究,也是從網上匯總的資料,英文的,應該不是很難。圖片不知道怎么上傳,唉,姑且先這么看著吧。
             

            How to communicate Windows 8 UI app (Metro Style app) and Desktop App, or how to translate data between these two style apps?

            Because Windows 8 UI ap runs in the sandbox, and for security, the App cannot send and access the desktop process, access the registry. But we have 5 methods as following to do it indirectly:

            1. transfer the data via file.(dual way)

             

            2. transfer the data via clipboard.(dual way)

             

            3. via WCF. (one way, Windows 8 UI app as client, Desktop App as server)

             

            4. via Network Socket

             

            5. via remote or cloud server, if you have one remote or cloud server, then your Windows 8 UI app and desktop app both can connect it and share the data.

             

            WCF:

            Windows Communication Foundation (WCF) is a framework for building service-oriented applications. Using WCF, you can send data as asynchronous messages from one service endpoint to another. A service endpoint can be part of a continuously available service hosted by IIS, or it can be a service hosted in an application. An endpoint can be a client of a service that requests data from a service endpoint.

            WCF server features are available in .NET 4.5 but the Metro (core) profile is a client profile only. You cannot host a WCF service in Windows 8 metro app, because they run in a sandboxed environment.

            WCF in Metro apps – supported functionality

            Bindings -

            BasicHttpBinding

            NetTcpBinding

            NetHttpBinding

            CustomBinding

            Binding elements -

            BinaryMessageEncodingBindingElement

            TextMessageEncodingBindingElement

            ConnectionOrientedTransportBindingElement

            SslStreamSecurityBindingElement

            WindowsStreamSecurityBindingElement

            TcpTransportBindingElement

            Http(s)TransportBindingElement

            TransportSecurityBindingElement

            Encoding -

            Text, Binary

            Security modes -

            None, Transport, TransportWithMessageCredential, TransportCredentialOnly (for BasicHttpBinding)

            ClientCredentialType -

            None, Basic, Digest, Negotiate, Ntlm, Windows

            Transfer Mode -

            Buffered, Streamed, StreamedRequest, and StreamedResponse

            Serializers -

            DataContractSerializer, DataContractJsonSerializer, XmlSerializer

            Miscellaneous -

            ChannelFactory

            DuplexChannelFactory

            CallbackBehavior

             

            Not support:

            There aren't any plans yet to support any of the WS-* features including wsHttpBinding

            WCF's NetNamedPipeBinding and NetTcpBinding (over localhost) wouldn't be available anyway due to the restrictions in metro

            Defferences:

            Configuration is not supported for Metro styled apps so WCF generates the binding and other configuration in code. All binding properties need to be set on the binding in the code itself.

            The XmlDictionaryReaderQuotas are not exposed in the preview version in Win8P - they are going to be in the latest version – therefore there is no way to configure that one remaining property (maxDepth) in Win8 preview right now.

            For you - while developing metro apps - you just need to be aware that:

            1) You need to make all configuration in code.

            2) You need to make all service calls async using the task based pattern.

             

            Here are some references can help when you are using WCF in metro:

            1. WCF in Windows 8 Metro styled apps? Absolutely supported

            http://blogs.msdn.com/b/piyushjo/archive/2011/09/22/wcf-in-win8-metro-styled-apps-absolutely-supported.aspx

            2. Calling a WCF service from a Metro application

            http://blogs.msdn.com/b/piyushjo/archive/2011/10/10/calling-a-wcf-service-from-a-metro-application.aspx

            3.WCF in Metro apps – supported functionality

            http://blogs.msdn.com/b/piyushjo/archive/2011/10/19/wcf-for-metro-apps-supported-functionality.aspx

            4.More information is here:

            http://blogs.msdn.com/b/piyushjo/

            5. Information in MSDN Library:

            http://msdn.microsoft.com/en-us/library/hh556233.aspx

            posted on 2012-09-04 13:10 Dino-Tech 閱讀(459) 評論(0)  編輯 收藏 引用
            久久精品国产第一区二区三区| 国产精品一区二区久久不卡 | 久久最新免费视频| 99热都是精品久久久久久| 狠狠久久亚洲欧美专区| 999久久久免费精品国产| 国产精品一区二区久久| 国产精品毛片久久久久久久| 久久久青草久久久青草| 99久久精品国产免看国产一区| 国内精品伊人久久久影院 | av午夜福利一片免费看久久| 亚洲第一永久AV网站久久精品男人的天堂AV| 精品水蜜桃久久久久久久| 久久精品成人欧美大片| 伊色综合久久之综合久久| 一本色综合网久久| 日韩精品久久久久久| 亚洲国产婷婷香蕉久久久久久| 久久亚洲美女精品国产精品| 亚洲成人精品久久| 久久亚洲国产成人影院| 久久婷婷国产综合精品 | 免费无码国产欧美久久18| 99久久免费国产精精品| 亚洲av日韩精品久久久久久a| 日韩欧美亚洲综合久久影院Ds | 国产A级毛片久久久精品毛片| 亚洲中文字幕无码久久精品1 | 精品久久久久国产免费| 国内精品九九久久久精品| 久久夜色精品国产欧美乱| 奇米影视7777久久精品| 精品蜜臀久久久久99网站| 久久亚洲AV成人无码国产| 日日噜噜夜夜狠狠久久丁香五月| 久久综合久久美利坚合众国 | 99re这里只有精品热久久| 男女久久久国产一区二区三区| 日韩十八禁一区二区久久| 欧美日韩精品久久久久|