WCF client in .NET Core

Hello,

DataStoreClient, CachedDataStoreClient, and their async versions are supported in client .NET Core apps (for instance, Xamarin).
We have just cut off the methods used to automatically create these IDataStore objects from a connection string:

C#
//DevExpress.Xpo\XpoDefault.cs  
#if !DXPORTABLE && !DXCORE3  
        static IDataStore CreateWCFWebServiceStore(string connectionString) {  
            EndpointAddress address = new EndpointAddress(connectionString);  
            BasicHttpBinding binding = new BasicHttpBinding();  
            if(!string.IsNullOrEmpty(connectionString) && connectionString.StartsWith("https://")) {  
                binding.Security.Mode = BasicHttpSecurityMode.Transport;  
            }  
            binding.MaxReceivedMessageSize = Int32.MaxValue;  
            binding.ReaderQuotas.MaxArrayLength = Int32.MaxValue;  
            binding.ReaderQuotas.MaxDepth = Int32.MaxValue;  
            binding.ReaderQuotas.MaxBytesPerRead = Int32.MaxValue;  
            binding.ReaderQuotas.MaxStringContentLength = Int32.MaxValue;  
            return CreateWcfServiceStore(connectionString, address, binding);  
        }  
...  

The only reason for this is not to add extra dependencies required to create bindings. For instance, BasicHttpBinding requires https://www.nuget.org/packages/System.ServiceModel.Http/; other bindings require other Nuget packages.
XPO developers can create and configure DataStoreClient and other XPO APIs as well as standard bindings in their client apps manually.

The only limitation is about the WCF hosting, because .NET Core itself does not support the ServiceHost API (this is out of our control, though):
    https://github.com/dotnet/wcf/issues/2559
    https://github.com/dotnet/wcf/issues/1200#issuecomment-356422289

XPO developers can still host their data services under the full .NET Framework and have .NET Core-based clients as consumers.

Let me know if you require any further clarification.