Hi,
Hello Gianluca,
We are sorry to hear that you have this issue.
It is not very clear which exact product you are using, GroupDocs.Viewer for .NET or GroupDocs.Comparison for .NET? With GroupDocs.Comparison you cannot display documents, and with GroupDocs.Viewer you cannot compare them.
GroupDocs.Comparison for .NET contains types and methods which are present in the GroupDocs.Viewer, but, independently of this, you cannot open document using the GroupDocs.Comparison for .NET. If you will try to do this, it will fail: all requests will have the HTTP 404 responses.
Thanks.
The issues you have found earlier (filed as WEB-1223;WEB-1422) have been fixed in this update.
This message was posted using Notification2Forum from Downloads module by GroupDocs Notifier.
The issues you have found earlier (filed as DOCOMPARE-684;DOCOMPARE-686;DOCOMPARE-688) have been fixed in this update.
This message was posted using Notification2Forum from Downloads module by GroupDocs Notifier.
The issues you have found earlier (filed as DOCOMPARE-688;DOCOMPARE-685;DOCOMPARE-686) have been fixed in this update.
This message was posted using Notification2Forum from Downloads module by GroupDocsNotifier.
Hi,
Hi,
- comparing pdf documents, there is everytime the last report page but i disable it on comparison widget initialization
- can’t debug javascript on entire application because the tool enable all js optimizations causing the minimization of them. This was a bug resolved in some release ago.
- compare on pptx files doesn’t work
- comparing xls files, the pictures aren’t shown
- didn’t find a method to clean the compare result file in temp folder. In a post forum someone wrote me that this will be a feature on some future release.
Hello Gianluca,
Sorry for the delay. While our developers are working on a list of reported issues, we have prepared a special project, which illustrates, how to use both GroupDocs.Viewer and GroupDocs.Comparison in a single ASP.NET WebForms project. Here it is. All necessary libraries are already included into the project, so you can unpack it, open with MS Visual Studio and run.
We will answer on all other items in this forum thread soon. Again, sorry for the delay.
Hi Denis,
Hello Gianluca,
Thanks for waiting. Yes, I admit that collaborative work of both libraries in a single MVC project is not such trivial as in the WebForms. But it is possible. Here you will find an updated version of the “SeveralLibs” solution. It contains two projects; with the first one (ViewerAndComparison) you are already familiar, but the second – ViewerAndComparisonMVC – contains what you need. From this project you can see how the GroupDocs.Viewer and GroupDocs.Comparison libraries can be used in a single project and work simultaneously. In short:
- You should not use a Viewer.InitRoutes() and should use HTTP‑handler descriptors in a web.config, like in the WebForms project.
- You should use a .UseHttpHandlers(true) in the GroupDocs.VViewer widget.
- You should exclude document‑viewer/ route from RouteCollection. (screenshot)
Of course, this should be considered a temporary solution. Our developers are working on enabling a GroupDocs.Viewer functionality via a single GroupDocs.Comparison library, but this is not trivial, because the GroupDocs.Comparison library contains a modified version of GroupDocs.Viewer.
When we have some news, we will notify you in this forum thread. And, of course, all other reported issues are under investigation.
Thanks.
Hi,
- comparing pdf documents, there is everytime the last report page but i disable it on comparison widget initialization
- compare on pptx files doesn’t work ( i uploaded the files, named testpptx.pptx and testpptx2.pptx on drive shared folder)
- comparing xls files, the pictures aren’t shown
- didn’t find a method to clean the compare result file in temp folder. In a post forum someone wrote me that this will be a feature on some future release.
- with some pdf file there are characted rendered in a bad way (look for the first page on test.pdf)
- some eml doesn’t contain all correct datas
- Compare doesn’t see the insertion of images
- rendering a document with a lot of pages cause a popup in older version of internet explorer (like IE8) for javascript slow execution
- xml can’t be viewed but setting his extension to html it render in the correct way. Can’t be done this internally by viewer?
- using html rendered mode and also rendering in this way the tumbnails, there is a text overflow on thoses (test it with testdocx.docx)
- ppt files render in very very slow time
Hello Gianluca,
Sorry for the delay.
-
Using the GroupDocs.Viewer functionality from GroupDocs.Comparison
As you mentioned before, the previous version of GroupDocs.Comparison allowed using GroupDocs.Viewer functionality without problems. However, it was a security bug: a user could purchase a single GroupDocs.Comparison license and use both products simultaneously. That “feature” was blocked in later versions.
You have a GroupDocs.Total license, and we have a feature request to unblock GroupDocs.Viewer when a GroupDocs.Total license is applied. Currently there is no estimate for when this will be implemented. It would be convenient to get rid of aliases,usingkeywords, and similar work‑arounds, but you will need to wait for this feature before using both GroupDocs.Viewer and GroupDocs.Comparison together. -
Cleaning the compare result file in the temp folder
Yes, that was my oversight. We discussed this feature previously, and I need more information to implement it. At present theApp_Datafolder (or any other root storage folder) holds both the result files and the input files (“source” and “target” in GroupDocs.Comparison). GroupDocs.Comparison must distinguish input from output files to delete only the appropriate ones.
Please tell us how you imagine this method working, what behavior you expect, and what data you want to pass to it. For example:RemoveResult(resultFilename)– whereresultFilenameis the name of the file to be removed.- Or remove all files that match a specific criterion, such as a defined prefix in the filename.
In other words, let us know exactly what you want to achieve and the behavior you’d like to see.
-
Comparing XML files
GroupDocs.Comparison can compare XML files without problems if you rename them to*.txt.
-
Bug reproduction and estimates
All reported bugs have been reproduced and are in the process of being addressed. I cannot give an exact estimate right now; I need to contact the developers and discuss each bug individually. Please give us some time, and we will respond in this forum thread.
Sorry for the inconvenience.
Hi Denis,
Hi,
Hello Gianluca,
About the last issue you have reported: "5 (edit) i found that turning the project in release mode, i get the errors printed in viewer.png (attached in this post)"
As we understand, it occurs when using a GroupDocs.Viewer. There are several ways to solve it depends on which application pool mode you are using.
1. If you are using an integrated app pool mode, please make sure that there is a line in the “system.webServer -> handlers” in the web.config.
2. If you are using a classic app pool mode:
2.1. Make sure that there is a in the “system.web -> httpHandlers” in the web.config.
2.2. Make sure that there is a
in the “system.webServer -> handlers” in the web.config.
Thanks.
Hello Gianluca,
A list of different tickets is attached to this forum thread, you should be able to see them in the top of the thread, along with the first post, in the left side. From that list you can see that two issues are already fixed. In particular, an issue when ArgumentOutOfRangeException exception is thrown when comparing two PDF files, and ability to display a XML without renaming it to the TXT (at this moment it was done only for GroupDocs.Viewer). Other bugs and features are still in progress. Sorry for that.
Thanks.
Hi,
Hello Gianluca,
Perfect, one problem less. “The bug WEB-1539 is reported as “won’t fix”, what’s the linked signal” - yes, because this “bug” is called a “Font-related HTTP-requests (WOFF and TTF) have HTTP 404 response in any cases (see details)”, and it was solved by me and by you (“…i resolved this last issue on my own editing the same tip you wrote…”). In other words, this problem is not a bug, and it is solved. That’s why - “won’t fix”.
About terms - I’ll chat with my management and will come back to you as soon as possible.
Ok, i asked you for the wont fix bug because i didn’t see the related description by this post forum!
1 , a , )</font></div><div><font color="#0000ff"> in ..(Document , String , Stream , HtmlSaveOptions )</font></div><div><font color="#0000ff"> in Aspose.Pdf.Document.Save(String outputFileName, SaveOptions options)</font></div><div><font color="#0000ff"> in ..()</font></div><div><font color="#0000ff"> in ..(String path, FileType type, options)</font></div><div><font color="#0000ff"> in ..(String path, FileType type, options)</font></div><div><font color="#0000ff"> in Groupdocs.Engine.Viewing.HtmlViewingService.GenerateHtml(String filePath, Func2 htmlWithImageCreator, String prefixForResourceUrlsInHtml, String prefixForResourceUrlsInHtmlFiles, Nullable1 firstPageParam, Nullable1 pageCountParam, Boolean usePngImagesForHtmlBasedEngine, Boolean convertWordDocumentsCompletely, Boolean ignoreDocumentAbsence, Boolean saveToCustomTempStorage, Boolean supportListOfContentControls, Boolean supportListOfBookmarks, Boolean embedImagesIntoHtmlForWordFiles)1 count, Nullable1 width, Nullable1 quality, Boolean usePdf, Nullable1 preloadPagesCount, Boolean convertWordDocumentsCompletely, String fileDisplayName, String watermarkText, Nullable`1 watermarkColor, WatermarkPosition watermarkPosition, Single watermarkFontSize, Boolean ignoreDocumentAbsence, Boolean supportPageRotation, Boolean supportListOfContentControls, Boolean supportListOfBookmarks, Boolean embedImagesIntoHtmlForWordFiles, String callback)Hello Gianluca,
Sorry for the delay.
1. About the file “test222.pdf”. We checked it using the latest version 2.9.1 of the GroupDocs.Viewer for .NET - it is displayed perfectly (without exceptions and rotations) in both image-based and HTML-based rendering modes. Please check the version of the GroupDocs.Viewer, which you are using, and please give us a source code of the GroupDocs.Viewer widget. About GroupDocs.Comparison - this particular “test222.pdf” file is useless in applying it to the GroupDocs.Comparison. GroupDocs.Comparison can compare only textual content, not the image data, while the “test222.pdf” in fact contains only one image without textual content at all.
2. About bugs and improvements in the GroupDocs.Comparison for .NET and in the .GroupDocs.Viewer for .NET. On the first page of this forum thread you can see a list of attached Jira tickets. Almost all “DOCOMPARE-XXX” tickets have a “Fixed” status. The new version of the GroupDocs.Comparison for .NET, which will contain all these fixes, should be released tomorrow, on March 26. The new version 2.10 of the GroupDocs.Viewer for .NET, which also would contain fixes of the issues, which were reported by you, will be released on March 31.
3. About performance of the GroupDocs.Viewer for .NET. There are several tips how to increase performance:
3.1. First of all, try to use a pre-generated cache if possible using a “DocumentCache” class. When you opens the documents using GroupDocs.Viewer, it converts them to the HTML-compatible form (HTML code, images, CSS, JS and so on) on the fly, and this process takes time depends on the size and complexity of the document. By using the “DocumentCache” class, you can pre-generate document cache before opening an actual document in the browser; so in the moment, when the end-user will want to open the document, it will be opened almost instantly.
3.2. Try to use HTML-based rendering mode (“UseHtmlBasedEngine(true)” method) if it is suitable for you and there are no document distortions.
3.3. Use “PreloadPagesCount(1)” method. When using this method GroupDocs.Viewer will begin to load document to the client-side when first page of the document will be converted. When this method is not used, GroupDocs.Viewer converts all pages of a document and only then sends it to the client-side.
3.4. Use “MinimumImageWidth(value)” method. MinimumImageWidth: if set, the Viewer will load page images with the specified width from the server when starting. It will not load page images from the server again after zooming if the current page image size is smaller than the value specified and if the original (not scaled) page image size is smaller than the value specified. It means that in most cases the GroupDocs.Viewer will load page images only once and will not reload them after zooming in/out.
3.5. If this is possible for your business-logic, disable thumbnails (“ShowThumbnails(false)”).
3.6. If this is possible for your business-logic, disable ability to select text by using “SupportTextSelection(false)” method.
3.7. Use “ShowViewerStyleControl(false)” method - it will disable “double page flip” option and will increase performance.
Thanks. If you will have more questions please feel free to contact us.