Need help with SoapCore?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

609 Stars 253 Forks MIT License 869 Commits 175 Opened issues


SOAP extension for ASP.NET Core

Services available


Need anything else?

Contributors list


NuGet Version

SOAP protocol middleware for ASP.NET Core

Based on Microsoft article: Custom ASP.NET Core Middleware Example.

Support ref\out params, exceptions. Works with legacy SOAP\WCF-clients.

Getting Started


The following frameworks are supported:

  • .NET Core 3.1 (using ASP.NET Core 3.0)
  • .NET Core 3.0 (using ASP.NET Core 3.0)
  • .NET Core 2.1 (using ASP.NET Core 2.1)
  • .NET Standard 2.0 (using ASP.NET Core 2.1)

.NET Core 2.2 / ASP.NET Core 2.2 is not explictly supported, but will probably work. We suggest upgrading to .NET Core 3.0 since .NET Core 2.2 is only supported until December 23, 2019. If you are using .NET Framework, and you cannot migrate to .NET Core, we recommend downgrading to Core 2.1 since it's an LTS release and will be supported for some time.


PM> Install-Package SoapCore

There are 2 different ways of adding SoapCore to your Core website. If you are using ASP.NET Core 3.0 or higher with endpoint routing enabled (the default):

In Startup.cs:

public void ConfigureServices(IServiceCollection services)

public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory) { app.UseRouting();

app.UseEndpoints(endpoints => {
    endpoints.UseSoapEndpoint<servicecontractimpl>("/ServicePath.asmx", new BasicHttpBinding());


If you are using ASP.NET Core 2.1 (i.e., on .NET Framework, .NET Core 2.1, or another .NET Standard 2.0 compliant platform):

public void ConfigureServices(IServiceCollection services)
public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)
    app.UseSoapEndpoint("/ServicePath.asmx", new BasicHttpBinding());


public static void Main(string[] args)
    var host = new WebHostBuilder()

Using with legacy WCF/WS

It is possible to use SoapCore with .net legacy WCF and Web Services, both as client and service.

Primary point here is to use XmlSerializer and properly markup messages and operations with xml serialization attributes. You may use legacy pre-generated wrappers to obtain these contracts or implement them manually. Extended example is available under serialization tests project.

Using with external WSDL / XSD schemas

There is an optional feature included where you can instead of generating service description from code get the service description from files stored on the server.

To use it, add a setting like this to appsettings

 "FileWSDL": {
    "UrlOverride": "",
    "WebServiceWSDLMapping": {
      "Service.asmx": {
        "WsdlFile": "snapshotpull.wsdl",
        "SchemaFolder": "Schemas",
        "WsdlFolder": "Schemas"
    "VirtualPath": ""
  • UrlOverride - can be used to override the URL in the service description. This can be useful if you are behind a firewall.
  • Service.asmx - is the endpoint of the service you expose. You can have more than one.
  • WsdlFile - is the name of the WSDL on disc.
  • SchemaFolder - if you import XSD from WSDL, this is the folder where the Schemas are stored on disc.
  • WsdlFolder - is the folder that the WSDL file is stored on disc.
  • VirualPath - can be used if you like to add a path between the base URL and service.

To read the setting you can do the following

In Startup.cs:

var settings = Configuration.GetSection("FileWSDL").Get();
settings.AppPath = env.ContentRootPath; // The hosting environment root path

app.UseSoapEndpoint("/Service.asmx", new BasicHttpBinding(), SoapSerializer.XmlSerializer, false, null, settings);

If the WsdFileOptions parameter is supplied then this feature is enabled / used.


Tips and Tricks

Extending the pipeline

In your ConfigureServices method, you can register some additional items to extend the pipeline: * services.AddSoapMessageInspector() - add a custom MessageInspector. This function is similar to the

in WCF. The newer
interface allows you to register multiple inspectors, and to know which service was being called. * services.AddSingleton() - add a custom OperationInvoker. Similar to WCF's
this allows you to override the invoking of a service operation, commonly to add custom logging or exception handling logic around it.

How to get custom HTTP header in SoapCore service

Use interface IServiceOperationTuner to tune each operation call.

Create class that implements IServiceOperationTuner. Parameters in Tune method: * httpContext - current HttpContext. Can be used to get http headers or body. * serviceInstance - instance of your service. * operation - information about called operation.

public class MyServiceOperationTuner : IServiceOperationTuner
    public void Tune(HttpContext httpContext, object serviceInstance, SoapCore.ServiceModel.OperationDescription operation)
        if (operation.Name.Equals("SomeOperationName"))
            MyService service = serviceInstance as MyService;
            string result = string.Empty;

        StringValues paramValue;
        if (httpContext.Request.Headers.TryGetValue("some_parameter", out paramValue))
            result = paramValue[0];



Register MyServiceOperationTuner in Startup class:

public class Startup
    public void ConfigureServices(IServiceCollection services)
        // ...
        services.AddSoapServiceOperationTuner(new MyServiceOperationTuner());
    // ...

Change your service to get the possibility to store information from http headers:

public class MyService : IMyServiceService
    // Use ThreadLocal or some of thread synchronization stuff if service registered as singleton.
    private ThreadLocal _paramValue = new ThreadLocal() { Value = string.Empty };

// ...

public void SetParameterForSomeOperation(string paramValue)
    _paramValue.Value = paramValue;

public string SomeOperationName()
    return "Param value from http header: " + _paramValue.Value;



See Contributing guide


Made with contributors-img.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.