-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable Data Contract Serialization for Remoting Exceptions #629
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe there should be changes to the proxy factory creation as well https://github.com/microsoft/Omex/blob/main/src/Services.Remoting/Client/OmexServiceProxyFactory.cs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The change looks fine, but I'd suggest adding some additional tests to the public/internal APIs that consume these to validate the behaviour.
We want to discontinue usage of binary formatter based serialization because of security implications. With this change we will switch to data contract based based serialization for remoting exceptions.
More information: https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-reliable-services-exception-serialization