Viewer and Compare problems

GroupDocs.Viewer Product Family
81

Hi Gianluca,


We plan to resolve the pdf issue in the next version of the library, but because of that that we can’t guarantee it with 100% sure I can’t share the exact date. Our GroupDocs.Viewer product team works on this task, but I’m afraid that I don’t have much news about the issue right now. The issue is with 3d party library and it’s hard to fix the issue without their help. We also are waiting for good news from them, but there is no update for them at this moment. When I will get any news I will notify you.

As for the tif printing issue - This issue is not a bug of the Groupdocs.Viewer, but rather a bug of a browser, which cannot prepare a document for printing properly. It occues not only in the landscape mode, but in book mode too. It also can be observed in Mozilla Firefox although indent on the right side is much lesser.

Development team of the Groupdocs.Viewer knows about this problem and because of it Groupdocs.Viewer contains an ability to perform the PDF-printing (.UsePdfPrinting(true)). In this mode Groupdocs.Viewer prepares an exact PDF-version of the original document, which can be printed from within the browser or other 3rd-party software like Adobe Acrobat. When using this mode the resultant representation of the document cannot be distorted by the browsers.

Best regards.
82

Hi Pavel,

in particular, which bugs have been fixed in this version? The resource load error or the Aspose.Cells error? thanks

Gianluca
83

Hi Gianluca,


In this version such bugs are fixed:
1. Error opening xls file - when it were thrown in the VS
2. Errors on pdf characters rendering on first page
3. With ppt parte5_corsoangularjs.pptx on slide 18 chars are displaced
4. As for the issue with the cache when you need to reload the document - does the solution that we suggested in the previous posts (use different file names) suitable for you?

Also please don’t forget to add HTTP handler from my previous reply.

Thank you.
84

As i’m running on IIS 7 i don’t have to add the handlers on system.web section, as i saw on MS forums. By the way, i added the handler on system.webserver section but can’t see bugs as resolved, are them resolved using virtualScrolling active?

Thanks,
Gianluca
85

Hi Gianluca,


Yes, we tested them with virtualScroling and your project example (as you can see on the screenshots: xlsx , bluedrive.pdf and pptx). We strongly recommend you to add the handler (example of the web.config attached) in other case we can’t guarantee the it will work fine.

Thank you.

86

This is my system.webserver section:



and this in system.web

What’s wrong?


As note, now i’m running on .net MVC project and in your web.config example, there is a GetResourceForHtmlHandler duplicate. It’s correct?


87

By the way, the trick for document in cache didn’t work, also deleting all the temp folder. It seems like there is some session or cache for documents. The bug cannot be replicated if use document in cache variable is set to false

88

Hi again,


You are right in case using MVC project type you don’t need the handlers for Viewer. You just need to ensure that you have such block:
<system.webServer>
</system.webServer>

As for the cache question - in addition to the cache of the project you need to clear the IE browser cache because the IE very rigid system of caching.

We can prepare an example which will show how to re-read the document for example on button click but this approach will not use the iframe. Instead of the iframe it will get the Viewer code from the controller and integrate it in to the web page. If you need such example please notify us.


Thank you.
89

For document cache we need of a solution that doesn’t need to clear the cache cause this cannot be done on js side (i think). Probably you can act on avoid caching on client side by some response header. By the way, this issue is replicated only with iframe so we need a solution in this case (and the delete of temp folder was done for tests but cannot be the solution or a part of this). In this first case i’m talking about a .net classic project (you must know that we are using your viewer on 2 projects, one .net and the other .net MVC).


For MVC project, these paramethers was already setted on web config but bug resolution doesn’t seems to work and i don’t know why,

Gianluca
90

Hi,


Ok I will prepare such MVC example for you. I think it will be ready today.

When I will finish with it I will come back to you here.

Thank you.
91

If possible, give priority to .net classic project because we have more stringent times with this project.


Thanks

Gianluca
92

Hi,


Ok, I just need to clarify what you mean under classic .net project

Thank you
93

Sorry for the wrong name, i mean .net project (the classic was referred to the managed pipeline mode on application pool)

94

To be sure, i simply edited your test project to replicate the bugs of xls files. Please try on this (on MVC and web forms projects)


Gianluca

95

Hi Gianluca,


We have prepared the example project which will work with our iframe and in the classic mode. Also this sample shows how to integrate the Viewer in way that it will reload to changed document correctly. Please download it here . The only thing that you will need to add (if needed) is a JavaScript code which will hide/show the Viewer block on some event (for example button click or document selection).

Also here is a video screencast of how it works on our side.

Thank you.

96

Hi Pavel,

sorry for the delay but in this two weeks i had a little health problem. By now, looking at the project, it seems that the key feature is the request of viewer code via ajax request. Is it correct? I’ll try this on our project by now.
Thanks
Gianluca
97

Hi Gianluca,


Hope your health is better. Yes, the main idea is to get Viewer code via ajax instead of iframe. This approach is much more stable and reliable if to use IE browser and all other browsers.

Best regards.