modeling - Aspose.Words for .NET

  1. Aspose.Words for.NET V24.4

    릴리스 노트: indent reported by AW model is different from MS Word. InvalidOperationException is thrown upon rendering document with ShowInBalloons.Format. NotSupportedException is thrown upon saving document as DOC ...

  2. Aspose.Words for.NET V23.9

    릴리스 노트: if metered license applied. Document.UpdateFields() throws 'Invalid document model. Operation can not be completed.'. Missing characters after converting PDF to DOCX. The size of "Sigma" ...

  3. Aspose.Words for.NET V23.10

    릴리스 노트: in TXT-model-HTML conversion. Added the ability to copy data point format/properties to/from another data point or series defaults. Set/get color of chart title. Change the font of chart title. Added a writing ...

  4. Aspose.Words for.NET V23.6

    릴리스 노트: issue. Formatting of hyperlinks inside IF field is changed after updating fields. DOCX to PDF merging issue. Add feature to merge PDF documents without parsing to flow document model. DOCX merging issue, ...

  5. Aspose.Words for.NET V23.4

    릴리스 노트: Adds the ability to set the distance between a table and surrounding text. Added the ability to set the distance between a table and surrounding text. Added a simple way to work with series and axes of combination charts. Added new public properties connected to relative shape positioning and ...

  6. Aspose.Words for.NET V22.12

    릴리스 노트: container table height or width. Word to PDF conversion- equation is missing from the chart. Table left indent in AW model does not match MS Word UI for an XML document. Some font names in Noto fallback ...

  7. About Aspose.Words for.NET

    설명: documents, without the need for Microsoft Word environment to be installed on the system. This.NET library is a collection of classes and methods that rely on the Document Object Model (DOM), giving developers ...

  8. Aspose.Words for.NET V22.4

    릴리스 노트: re-saving a PDF. Document model compatibility option value does not match MS Word UI. Font in SmartArt diagram is smaller than in MS Word. Table cell preferred does not match MS Word in Aspose.Words DOCX ...

  9. Aspose.Words for.NET 관련 정보

    설명: need for Microsoft Word environment to be installed on the system. This.NET library is a collection of classes and methods that rely on the Document Object Model (DOM), giving developers direct access to ...

  10. Aspose.Words for.NET V21.10

    릴리스 노트: for LINQ Reporting Engine. StructuredDocumentTagRangeStart\End pair removed from document model. Content overlaps in PDF. Document comparison does not show deletion of shape. System.IndexOutOfRangeException ...

  11. Aspose.Words for.NET V21.5

    릴리스 노트: for StylisticSet attribute in the document model. Added new methods to set checked and unchecked symbol for StructuredDocumentTag. Added the ability to write generator name (Aspose.Words x.x.x.x) in HtmlFixed ...

  12. Aspose.Words for.NET V21.1

    릴리스 노트: in an Aspose.Words Document model. Added the ability to bookmark a table’s column. Added the ability to get or set cell vertical alignment using TableStyle. Microsoft Word should now automatically pick default Icon ...

  13. Aspose.Words for.NET V20.10

    릴리스 노트: and numbering when convert HTML to DOCX. DrawingML becomes invisible when rendering to PDF. Extra spaces appear in Model (.ODT format). NullReferenceException when call UpdatePageLayout for specific document. ...

  14. Aspose.Words for.NET V16.8.0 released

    릴리스 노트: and improvements in model and flow formats. Hijri/Lunar, Hebrew Calendar Date Field options supported. The analogue of NEXT fields added to LINQ Reporting Engine. ...

  15. Aspose.Words for.NET V17.2.0 released

    릴리스 노트: related to FitText are improperly read into the model of the.DOC document. Docx to Pdf conversion issue with TOC item rendering. Single Solid-line in word document converts double border for the images ...

  16. Aspose.Words was the clear winner for us.

    고객 리뷰: Aspose.Words was the clear winner for us.  First, it was the only one that converted my tests accurately every time.  Second, the licensing model was the best for our situation. Now, I'm not using Open XML ...