Skip to content
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

Integration or Redirection, in the ASP.NET application ? #136

Closed
hasanmansor opened this issue Nov 21, 2017 · 3 comments
Closed

Integration or Redirection, in the ASP.NET application ? #136

hasanmansor opened this issue Nov 21, 2017 · 3 comments

Comments

@hasanmansor
Copy link

hasanmansor commented Nov 21, 2017

Hello Everyone,

I have an ASP.NET webform application and I want to integrate the OHIF viewer into this application. Can anybody tell me whats the best way to integrate (either putting OHIF viewer directly in the ASP.NET solution or redirecting the ASP.NET webform to the standalone OHIF). I would really appreciate your help.

Hasan

@hasanmansor hasanmansor changed the title Integration into ASP.NET (Question) Integration or Redirection, in the ASP.NET application ? Nov 21, 2017
@swederik
Copy link
Member

Hi Hasan,

I would guess that it would be easiest to use the standalone viewer in this case, but I'm not really sure. Anybody else have any ideas?

@Zaid-Safadi
Copy link
Contributor

@hasanmansor , I believe the standalone viewer is the best option for integrating with an ASP.NET app unless you will run your own customized version of the full viewer.

The standalone viewer now supports a url query parameter to retrieve the study (see issue #91)

I have implemented an example of this integration in the DICOMweb-js which you can see here:
http://dicomweb.azurewebsites.net/

@hasanmansor
Copy link
Author

Thank you @swederik and @Zaid-Safadi !

Yeah, it seems the better option to use the standalone viewer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants