Free Support Forum - groupdocs.com

Can pass already convert jpg and js to viewer?


#1

Hi

I am use Group Doc viewer for .net and version is 2.1.2 in asp.net using vb language,when each time open file,it will convert jpg and js file into stored path that we declare in Global.asax.it will create jpg and js file in folwiing folders with file name and date,time
\temp\Cache\24-25.jpg\2014-08-06T09_42_53
\temp\Processing\24-25.jpg\2014-08-06T09_42_53

my file name is 24-25.jpg.so form above

1.Which folder jpg and js take and show in viewer ?
2.When first time convert and i store files form Processing folder in sql server and when open same file (24-25.jpg) can i pass stored file form sql server to viewer ? i.e. i can retrieve and save that file in folder which mention in Global.asax.file.
3.First i can open file,if i close and view again same file,cant view the viewer,it always show loading content progress bar.
4.When try to open 3 file continuously,i.e i will open first file and close,and open next file,but second time it show always show loading progress bar.


Regards
Aravind

#2

Hello Aravind,

We are sorry to hear that you have such issue.

GroupDocs.Viewer of course can display JPEG files but the same can do every browser, so using GroupDocs.Viewer for displaying JPEGs is overkill. Now what about your list:

1. Folder “Processing” stores intermediate results of the converting process, it should always be local. In fact, it is required by GroupDocs.Viewer as a place for internal work. Folder “Cache” can be remote; when conversion is completed, files are copied from “Processing” to “Cache”. So, regarding to your question, it is “Cache”.

2. It is not clear what you want to do. Do you want to store cached files in the SQL Server and then insert them to the GroupDocs.Viewer’s cache? If yes, the purpose of such operation is not understandable - the only “advantage” of such operation will be performance degradation.

3. We need the source code of the page and the way how you load the file in order to reproduce it.

4. Maybe the document is the reason of such issue, maybe it is corrupted or not supported by the GroupDocs.Viewer. We need the source code of the page and a “problematic” document.

If you will have more questions please feel free to contact us.