Async WCF call with ChannelFactory and CreateChannel

前端 未结 3 1697
南旧
南旧 2021-02-06 00:47

I work on project where web application hosted on web server calls WCF services hosted on the app server. Proxy for WCF calls is created by ChannelFactory and calls are made via

相关标签:
3条回答
  • 2021-02-06 01:47

    Unfortunately no, there is not.

    The async methods you get from svcutil are generated in the proxy based on your interface. There is nothing in the raw WCF channel like this.

    The only way is to alter the service reference to have native async calls, which you don't want, or to create your own wrapper around the channel and implement them yourself like the generated proxy does.

    0 讨论(0)
  • 2021-02-06 01:47

    You can automatically generate new interface that contains async versions of methods from original interface using T4 and use it in ChannelFactory without changing interface on server side.

    I used NRefactory to parse original and generate new C# source code and AssemblyReferences.tt to use nuget packages in T4 template:

    <#@ template debug="false" hostspecific="true" language="C#" #>
    <#@ include file="AssemblyReferences.tt" #>
    <#@ assembly name="System.Core" #>
    <#@ import namespace="System.Linq" #>
    <#@ import namespace="ICSharpCode.NRefactory.CSharp" #>
    <#@ output extension=".cs"#>
    <# 
    var file = System.IO.File.ReadAllText(this.Host.ResolvePath("IUserService.cs")); 
    if(!file.Contains("using System.Threading.Tasks;"))
    { #>
    using System.Threading.Tasks;
    <# } #>
    <#
    CSharpParser parser = new CSharpParser();
    var syntaxTree = parser.Parse(file);
    
    
    foreach (var namespaceDeclaration in syntaxTree.Descendants.OfType<NamespaceDeclaration>())
    {
        namespaceDeclaration.Name += ".Client";
    }
    
    
    foreach (var methodDeclaration in syntaxTree.Descendants.OfType<MethodDeclaration>())
    {
        if (methodDeclaration.Name.Contains("Async"))
            continue;
    
        MethodDeclaration asyncMethod = methodDeclaration.Clone() as MethodDeclaration;
        asyncMethod.Name += "Async"; 
    
        if (asyncMethod.ReturnType.ToString() == "void")
            asyncMethod.ReturnType = new SimpleType("Task");
        else
            asyncMethod.ReturnType = new SimpleType("Task", typeArguments: asyncMethod.ReturnType.Clone());
    
        methodDeclaration.Parent.AddChild(asyncMethod, Roles.TypeMemberRole);
    }
    
    #>
    <#=syntaxTree.ToString()#>​
    

    You pass your interface file name to template:

    using System.Collections.Generic;
    using System.ServiceModel;
    
    namespace MyProject
    {
        [ServiceContract]
        interface IUserService
        {
            [OperationContract]
            List<User> GetAllUsers();
        }
    }
    

    To get new one:

    using System.Threading.Tasks;
    using System.Collections.Generic;
    using System.ServiceModel;
    
    namespace MyProject.Client
    {
        [ServiceContract]
        interface IUserService
        {
            [OperationContract]
            List<User> GetAllUsers ();
    
            [OperationContract]
            Task<List<User>> GetAllUsersAsync ();
        }
    }
    

    Now you can put it in factory to use channel asynchroniously:

    var factory = new ChannelFactory<MyProject.Client.IUserService>("*");
    var channel = factory.CreateChannel();
    var users = await channel.GetAllUsersAsync();
    
    0 讨论(0)
  • 2021-02-06 01:48

    Unfortunately, this isn't possible and there is a pretty good reason for it. CreateChannel returns an object that implements the provided interface (IUserService in your example). This interface is not async-aware, so there is no way it could return an object with the correct methods.

    There are two possible solutions:

    1. Create your own proxy that is able to call the WCF service. This means you need to write your own proxy (or let svcutil do it for you).
    2. Make sure IUserService is an async interface that returns tasks. This is supported in WCF 4.5 and later. This is what I often use. The major drawback is that it makes your service a bit complicated and you are required to invoke the methods async (which might also be considered an advantage).
    0 讨论(0)
提交回复
热议问题