On this page
NoteThis page contains release notes for GroupDocs.Comparsion for .NET 17.10
Below the list of the most notable features improvements and fixes for GroupDocs.Comparison 17.10:
- Authors were added to all changes
- Bug with changed styles in Note was fixed
- SaveImages and GetImages methods in Note were fixed
- Cell’s Aligner was improved
- Intermediate paragraph algorithm was added to Note
- Outline’s styles were added
- AlignWithoutPositioning algorithm was added to Note
- Note’s Summary page was fixed
- Comparison of headerFoters was added to PDF
|COMPARISONNET-1407||Add coordinates of Images as Styles||New Feature|
|COMPARISONNET-1395||Add ParagraphMerger||New Feature|
|COMPARISONNET-1387||Add set password to document for PDF||New Feature|
|COMPARISONNET-1409||Pdf Improvements:Check compare and add HeaderFooter to document||Improvement|
|COMPARISONNET-1408||Pdf Improvements: Update page properties||Improvement|
|COMPARISONNET-1402||Improve compare of comments in Comparison.Cells||Improvement|
|COMPARISONNET-1400||Refactoring for settings code||Improvement|
|COMPARISONNET-1396||Remove null checking from FeelChild method||Improvement|
|COMPARISONNET-1410||Fix summary page style||Bug|
|COMPARISONNET-1405||Fix Deep Changed Nodes||Bug|
|COMPARISONNET-1399||Fix saveImages and getImages methods for Comparison.Note||Bug|
|COMPARISONNET-1394||Bug with same text divided on different paragraphs||Bug|
|COMPARISONNET-1392||Bug with excess outline||Bug|
|COMPARISONNET-1385||issue in Getting author for the changes (Changeinfo)||Bug|
NoteThis section lists public API changes that were introduced in GroupDocs.Comparison for .NET 17.10. It includes not only new and obsoleted public methods, but also a description of any changes in the behavior behind the scenes in GroupDocs.Comparison which may affect existing code. Any behavior introduced that could be seen as a regression and modifies existing behavior is especially important and is documented here.
Was this page helpful?
Any additional feedback you'd like to share with us?
Please tell us how we can improve this page.
Thank you for your feedback!
We value your opinion. Your feedback will help us improve our documentation.