No description, website, or topics provided.
Switch branches/tags
Nothing to show
Clone or download
Latest commit d9384d5 Nov 18, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
Scripts Renamed assembly and external types to avoid conflict on Mono, Xamari… Nov 18, 2018
mcs Fix module name Nov 18, 2018
.gitattributes init Nov 17, 2018
.gitignore init Nov 17, 2018
Directory.Build.Props Add build scaffolding Nov 17, 2018
LICENSE init Nov 17, 2018 Update Nov 18, 2018
azure-pipelines.yml Add build scaffolding Nov 17, 2018
version.json Add build scaffolding Nov 17, 2018


This is the SoapFormatter and related classes taken from Mono and compiled for .NET Standard 2.0. Its goal is to enable serializing and deserializing SOAP XML for applications that have a dependency on that legacy format.

Build Status NuGet

The library is a code-compatible replacement, but has a different assembly identity. That means you must recompile code against this library. Three types were moved into a different namespace to avoid potential conflicts:

Header and HeaderHandler. Those are now in the System.Runtime.Remoting.Messaging.Legacy namespace and ISoapMessage is now in System.Runtime.Serialization.Formatters.Legacy.


See the sln file in mcs/class/System.Runtime.Serialization.Formatters.Soap.


.NET Core does not support serializing all of the same types that .NET Framework does. Noteably, Delegates, Type, and Assembly are not supported.


Use at your own risk. The formatter may have security implications in your code that you are solely responsible for.