Perfect! Build success with Visual Studio

Very very very thank Sébastien, the steps in the link below, it worked perfect …

https://groups.google.com/forum/#!topic/orthanc-users/AOUI-dU3RFk

You recommend steps for learning? I studied on the DICOM concept but now I would like to see how things are implemented, but I need to start by something more basic, was thinking of studying the code “MDW”, or the code that opens the door to DICOM communication, what do you suggest ?

Thank you
Marcelo

Very very very thank Sébastien, the steps in the link below, it worked perfect …
https://groups.google.com/forum/#!topic/orthanc-users/AOUI-dU3RFk

Fine :wink:

You recommend steps for learning? I studied on the DICOM concept but now I would like to see how things are implemented, but I need to start by something more basic, was thinking of studying the code “MDW”, or the code that opens the door to DICOM communication, what do you suggest ?

Instead of diving into the core of Orthanc (that handles the DICOM communications for you), I would highly suggest you to learn how to create plugins. This is the recommended way to contribute to Orthanc, it is well documented, and it allows you to play with DICOM worklists:
https://orthanc.chu.ulg.ac.be/book/contributing.html

If worklists are of interest to you, a good starting point would the source code of the “ModalityWorklists” plugin that is contained as a sample in the source distribution of Orthanc:
https://bitbucket.org/sjodogne/orthanc/src/default/Plugins/Samples/ModalityWorklists/

You might e.g. modify it so that it would handle the adding/removing of worklists through some REST API or some HL7 messaging (instead of reading it from a filesystem folder), which is something Orthanc users have asked in the past:
https://groups.google.com/d/msg/orthanc-users/1RFtbeq43r8/NAZwQjAaBAAJ

The Orthanc plugin SDK contains all the required primitives to achieve this goal.

Sébastien-

Thank you Sébastien!
I am following your recommendation … The materials help me a lot!

In the source code, see the files with extension “.c” and “.cpp” I can understand that is mixed, some things were created with language “C” and others with “C ++”, correct?

Thanks!
Marcelo

In the source code, see the files with extension “.c” and “.cpp” I can understand that is mixed, some things were created with language “C” and others with “C ++”, correct?

The native part of Orthanc (i.e. its core and its official plugins) is entirely coded in C++.

The Web applications (Web viewer and Orthanc Explorer) are written in HTML5/JavaScript.

The C code you see is either third-party dependencies, or the basic sample plugin.