Live Chat

Overview of Aspose.Words in .NET

Skip to end of metadata
Go to start of metadata

The Aspose.Words API in .NET
While trying to keep the API as straightforward and clear as possible, we decided to recognize and honor the common development practices of the platform. Therefore, Aspose.Words for .NET follows coding guidelines widely accepted by .NET developers. You can find examples of this below.

Namespaces

All classes in Aspose.Words are split into appropriate namespaces for easy access. The Aspose.Words namespace is the root and provides classes for generating, converting, modifying, rendering and printing Microsoft Word documents without utilizing Microsoft Word.

Namespaces in Aspose.Words for .NET
Aspose.Words
Aspose.Words.BuildingBlocks
Aspose.Words.Drawing

Classes

Wherever possible, class, method and property names resemble those of Microsoft Word Automation.

Class Name in Aspose.Words for .NET
Document
Paragraph

Enumerations

Example of the types of enumerations used in Aspose.Words.

Methods

Method names follow the accepted practices for the .NET platform.

Method Name in Aspose.Words for .NET
Document.Save
CompositeNode.GetChildNodes

Properties

Example of types of properties used in Aspose.Words.

Property Name in Aspose.Words for .NET
Font.Bold
PageSetup.LeftMargin

Indexed Properties

Examples of Indexed properties in Aspose.Words

Indexed Property in Aspose.Words for .NET
Style[int]
Style[string]

Implementations of Internal Interfaces

In Aspose.Words for .NET, only about 150 classes are public while the other 900 or so classes and interfaces are internal. It is possible in C# for a class to implement an interface in two ways: declare the methods of the interface as public, or declare them as explicit interface implementation methods. Most of the time we used explicit interface implementations so you don't see methods of the internal interfaces in the public API of Aspose.Words for .NET.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.