Spread ASP.NET 17
Spread for ASP.NET 17 Product Documentation / Developer's Guide / Namespaces Overview
In This Topic
    Namespaces Overview
    In This Topic

    In Spread for ASP.NET, namespaces are organized to contain objects according to how they are used in the Spread component. The Spread component comprises six namespaces. The objects in the component fall into these categories:

    For each of these there is a specific namespace. The namespaces are organized as follows:

    Namespace Description
    FarPoint.Web.Spread Provides the base classes, interfaces, enumerations, and delegates for Spread.
    FarPoint.Web.Spread.Chart Provides the base classes, interfaces, and enumerations for the Spread Chart component.
    FarPoint.Web.Spread.Data Provides the base classes and interfaces for data binding for the Spread spreadsheet component.
    FarPoint.Web.Spread.Editor Provides the base classes and interface for the controls used to edit cells.
    FarPoint.Web.Spread.Model Provides the base classes, interfaces, and enumerations for the Spread models.
    FarPoint.Web.Spread.Renderer Provides the base classes and interfaces for the controls used to render cells.

    The spreadsheet objects and event arguments are in classes in the main Spread namespace. For a discussion of how to work with these objects, refer to Shortcut Objects.

    The conceptual objects, the more abstract objects, are referred to as "models." These models are responsible for managing the style information, formatting, and data in the Spread component. These are found in the Model namespace. In Spread, you can use the default models or extend them through inheritance. Refer to Underlying Models for more information on models.

    The spreadsheet and cell type objects call the model objects. If you are new to working with Spread, or are new to developing in an object-oriented environment, you might want to use the spreadsheet and cell type objects at first, as you become familiar with features of Spread. However, intensive use of these objects can degrade your application’s performance.

    If you are an experienced programmer, you might want to use the model objects directly, instead of accessing them through the shortcut objects. If you want to extend Spread for ASP.NET, you must use the model objects to do so.