there is a bug in TaskHubWorker.AddTaskActivitiesFromInterface where each method of a registered interface is keyed by a weak "qualified name" that hits collisions when using C# code reuse features such as inheritance, generics, method overloading.
This is reproducible even with useFullyQualifiedMethodNames = true.
This PR fixes by making a stronger qualified name in "V2" methods for task registration and client creation.
It is essential to keep the "V1" methods for back-compatibility.
there is a bug in
TaskHubWorker.AddTaskActivitiesFromInterface
where each method of a registered interface is keyed by a weak "qualified name" that hits collisions when using C# code reuse features such as inheritance, generics, method overloading. This is reproducible even withuseFullyQualifiedMethodNames = true
. This PR fixes by making a stronger qualified name in "V2" methods for task registration and client creation. It is essential to keep the "V1" methods for back-compatibility.