-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error on study query #5
Comments
The exception seems to be happening in the static constructor of the class "DefaultDicomQueryElements". I'll need to get some information to assist you with this: Which branch of the server are you testing with, fo-dicom-integration or master? For the fo-dicom-integration please make sure you are using the Dicom libraries in the resources "Resources/Bin" folder: For the master branch, use the ClearCanvas dlls:
If using the above fixes your problem, please let me know the Dicom toolkit version number you are using causing the error. Otherwise, provide me with any instructions to help me reproduce. |
with clearcanvas verison i am not getting this error.right now i am using i have not hosted so far..i was just checking and running both client and On 26 August 2016 at 08:35, Xeos notifications@github.com wrote:
|
This should also work with fo-dicom dll that I have in my resources\bin folder. The version that I have is an update to fo-dicom v2.0 but < 3.0. Once v3.0 is released I'll update the project to use that. |
@dglecons I'm closing this ticket for now, if you still running into issues please let me know. I also have now a new branch "development" that is updated with the latest fo-dicom v3 pre release. |
question on the dicom cloud project
i get this error on study query from the demo project to cloud application
An exception of type 'System.TypeInitializationException' occurred in DICOMcloud.Wado.Core.dll but was not handled in user code
Additional information: The type initializer for 'DICOMcloud.Wado.Core.DefaultDicomQueryElements' threw an exception.
The text was updated successfully, but these errors were encountered: