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
dotnet-svcutil tool generates asynchronous client code that doesn't accept cancellation tokens. Calling these generated methods becomes problematic inside a cancellable task or thread in .Net 6. We can't just abort a thread anymore in netcore.
I know it's not a valid direct comparison, but swagger c# client generator produces client code with versions of methods that accept cancellation tokens, which allows the caller to abort a request mid-execution in a responsive way.
Is there a possibility that cancellation tokens will be supported by dotnet-svcutil generated code in the future? If not by default then maybe through some optional parameter.
The text was updated successfully, but these errors were encountered:
dotnet-svcutil tool generates asynchronous client code that doesn't accept cancellation tokens. Calling these generated methods becomes problematic inside a cancellable task or thread in .Net 6. We can't just abort a thread anymore in netcore.
I know it's not a valid direct comparison, but swagger c# client generator produces client code with versions of methods that accept cancellation tokens, which allows the caller to abort a request mid-execution in a responsive way.
Is there a possibility that cancellation tokens will be supported by dotnet-svcutil generated code in the future? If not by default then maybe through some optional parameter.
The text was updated successfully, but these errors were encountered: