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
Create WCF service with NetTCP binding with runtime as .Net framework 4.8
Create WCF client (Win forms exe) using WCF client packages 8.1 and runtime as .Net 8.0
Expected Results:
Both operations should return irrespective of the sequence of requests
Actual Results:
Scenario 1: If Sync call (button2_Click) is Invoked first, call never returns
Scenario 2: If Async call (button1_Click) is Invoked first and then Sync call (button_Click) is invoked, results are as expected
Scenario 3: Sync calls works fine provided async call was invoked at least once
No issue if client is running on .Net framework.
No issue if client is a console application on .Net 8.0
@mconnew , How to justify the above behavior with WCF client packages on .Net 8.0 ?
Your clarifications will help me to assess the feasibility of WCF client codebase migration to .Net 8.0
The text was updated successfully, but these errors were encountered:
Samba143
changed the title
WCF Client (.net8.0 Win form Exe) Call will Hung if Sync Method is Invoked
WCF Client (.net8.0 Win form Exe) Call will Hung if Sync Method is Invoked before Invoking any Async Method
Jan 20, 2025
Repro:
Expected Results:
Both operations should return irrespective of the sequence of requests
Actual Results:
Scenario 1: If Sync call (button2_Click) is Invoked first, call never returns
Scenario 2: If Async call (button1_Click) is Invoked first and then Sync call (button_Click) is invoked, results are as expected
Scenario 3: Sync calls works fine provided async call was invoked at least once
No issue if client is running on .Net framework.
No issue if client is a console application on .Net 8.0
@mconnew , How to justify the above behavior with WCF client packages on .Net 8.0 ?
Your clarifications will help me to assess the feasibility of WCF client codebase migration to .Net 8.0
The text was updated successfully, but these errors were encountered: