You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To avoid duplicate data contract name when using DataContract classes with same name, but different namespaces, I think it needs some mechanism for renaming data contract's name.
Found some referencable operation in ServiceBinder class that renames operation contract's name by using OperationAttribute.Name and OperationContractAttribute.Name
services and data types have quite a few differences; can you perhaps give a minimal but complete example of the scenario that is causing you a problem, and what you're seeing, so we don't talk past each-other?
To avoid duplicate data contract name when using DataContract classes with same name, but different namespaces, I think it needs some mechanism for renaming data contract's name.
Found some referencable operation in
ServiceBinder
class that renames operation contract's name by usingOperationAttribute.Name
andOperationContractAttribute.Name
protobuf-net.Grpc/src/protobuf-net.Grpc/Configuration/ServiceBinder.cs
Lines 162 to 165 in 062c184
The text was updated successfully, but these errors were encountered: