GroupDocs.Comparison For .NET 3.3.0 Release Notes
This page contains release notes for GroupDocs.Comparsion for .NET 3.3.0
Major Features
There are 12 improvements and fixes in this regular monthly release. The most notable are:
- Improved the comparison of tables for Comparison.Words
- Improved the comparison of tables for Comparison.PDF
- Improved Comparison.Cells performance
- Improved comparison for contents list for Comparison.Words
Full List of Issues Covering all Changes in this Release
| Key | Summary | Category |
|---|---|---|
| COMPARISONNET-792 | GroupDocs.Comparison.Words: Add page numbers comparison | New Feature |
| COMPARISONNET-818 | GroupDocs.Comparison Words: Add group shapes support | New Feature |
| COMPARISONNET-782 | Improve the comparison of tables for Comparison.Words: Some tables differ on two cell but algorithm not defined the tables as similar | Improvement |
| COMPARISONNET-783 | Comparison.Words: Improve comparison for contents list | Improvement |
| COMPARISONNET-817 | Improve cells performance | Improvement |
| COMPARISONNET-687 | Improve working with tables in Comparison.Pdf | Improvement |
| COMPARISONNET-698 | Fix bug when you can not open document with tables after comparison | Bug |
| COMPARISONNET-727 | Comparing Words: - Files generating zero output (no change is detected ) for attached files only | Bug |
| COMPARISONNET-736 | Some tables differ on two cell but algorithm not defined the tables as similar | Bug |
| COMPARISONNET-795 | GroupDocs.Comparison.Words: The target file is modification of source file but defined as different | Bug |
| COMPARISONNET-850 | Cannot open result file: graphics objects | Bug |
| COMPARISONNET-851 | Some images (or graphical objects) are not displayed | Bug |
Public API and Backward Incompatible Changes
This section lists public API changes that were introduced in GroupDocs.Comparison for .NET 3.3.0. 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.
None