Object model overview, Mapinfo.data namespace – Pitney Bowes MapXtreme User Manual

Page 68

Advertising
background image

Chapter 4: Understanding the MapXtreme Architecture

Object Model Overview

MapXtreme v7.1

68

Developer Guide

Object Model Overview

The MapXtreme Object Model is made up of many namespaces. A .NET namespace is a type
classification system that differentiates specific classes, methods, and properties from others with
the same name. By utilizing namespaces, .NET developers can avoid collisions between names of
objects and their methods and properties.

MapXtreme ships with a full-color poster of the key interfaces and classes and shows how they
relate to each other via namespace segregation. A PDF version of the poster is viewable from the
Learning Resources page, which is accessible from the Windows Start menu. Specifically, the
Learning Resources page can be accessed from: Start > All Programs > MapInfo > MapXtreme >
Learning Resources.

The list below contains several of the namespaces implemented in the MapXtreme Object Model. A
broad overview of each namespace is included in the following sections. Each description contains a
reference to the part of this manual that contains detailed information about it and its use.

MapInfo.Data Namespace

MapInfo.Data.Find Namespace

MapInfo.Engine Namespace

MapInfo.Geometry Namespace

MapInfo.Mapping Namespace

MapInfo.Persistence Namespace

MapInfo.Raster Namespace

MapInfo.Styles Namespace

MapInfo.WebControls Namespace

MapInfo.Tools Namespace

MapInfo.Geocoding Namespace

MapInfo.Routing Namespace

The complete object model is organized by namespace in the MapXtreme Programmer’s Reference,
which is integrated into Visual Studio.

If you have used MapX or the non-.NET version of MapXtreme (MapXtreme for Windows v3), be
sure to review

Appendix J: Migrating to MapXtreme

for a comparison of the two product’s object

models.

MapInfo.Data Namespace

The MapInfo.Data namespace contains the classes and interfaces that implement the MapInfo Data
Provider. The object model has several different classes to access data. Depending on the format in
which your data is stored, there are specific classes to use to access it. Additionally, we now
implement ADO.NET access to any data that is contained in formats not covered by any other class.
For details on the MapInfo.Data namespace, see

Chapter 8: Working with Data

and

Chapter 11:

Accessing Data from a DBMS

.

Advertising