As described in the title, MaxAsyncOpsInvoked and MaxAsyncOpsPerformed are not set while handling the association request.
As a result, it may remain 0, and the client will go into a deadloop in line 418 to line 511 in DicomClient.cs if I also use fo as store client.
there has been a release today. Version fo-dicom 5.1.2 has several fixes concerning dicomserver and dicomclient. Please check with the latest version and report, if the issue is still open.
As described in the title, MaxAsyncOpsInvoked and MaxAsyncOpsPerformed are not set while handling the association request. As a result, it may remain 0, and the client will go into a deadloop in line 418 to line 511 in DicomClient.cs if I also use fo as store client.