This change adds support for using custom serialization providers in the communication between ServiceFabric services. I've tested this change using Microsoft's sample JSON SerializationProvider, but any provider should be able to be passed in when the service is created at startup. Identical custom serializers will need to be passed into both the client facing service and the internal service.
For example, when using the JSON Serializer in ClientApp and DistributedCacheStore, we'd do the following to register the SerializationProvider:
This change adds support for using custom serialization providers in the communication between ServiceFabric services. I've tested this change using Microsoft's sample JSON SerializationProvider, but any provider should be able to be passed in when the service is created at startup. Identical custom serializers will need to be passed into both the client facing service and the internal service.
For example, when using the JSON Serializer in ClientApp and DistributedCacheStore, we'd do the following to register the SerializationProvider:
ClientApp/Startup.cs
DistributedCacheStore/DistributedCacheStore.cs