New to the viewer component here. My use case does not appear to blend with how the implementation of the viewer works based on your examples.
We have a multi tenant system where local disk storage is not available. Users click on a link with an ID of an attachment (www.appUrl.com/Files/DownloadFile/123).
Our controller fetches the file stream of this attachment (finds the blob data in SQL, then goes to blob) from the blob storage and serves it up as a stream to the front end so the users receive the “Save As” prompt.
Problem: We want to modify this experience so the user is redirected to a “viewer” page (instead of a download prompt) and the viewer renders the file stream in browser instead of a download. Then we want to offer an additional link on the viewer page for users to download the file as it works today. We also want to modify some of the controls on the viewer so its just a simple Read-Only document viewer with nothing else (I did see a post somewhere how to customize this but it did not seem simple).
I am unclear how to achieve this, as I expected there to be a viewer “View” implementation that takes a Model with some sort of blob reference, stream reference, or raw HTML set on the backend. Or, a view page that has client side JS that can call a server side endpoint to fetch whatever the content is to render. As I understand it, the viewer component can save the File Stream as HTML to another stream, but how to pass that to the front end is missing.
Can you point me in a proper direction? I am a GroupDocs.Total license member.
I should note: We are using .Net Core 5 with MVC and some hybrid approaches (small API controller for various front end things). This is hosted as an App Service inside azure.