ESRI MapObjects Version 2.

3
May 20th 2004
Release Notes
Copyright 1998-2004 Environmental Systems Research Institute, Inc.
Portions Copyright Cimmetry Systems inc. (CSI) 1993-1995
MrSID, MrSID Decompressor, and the MrSID logo are trademarks of LizardTech, Inc. used with
permission. Portions of this computer program are copyright 1995-1998 LizardTech and/or the
University of California. All rights reserved. MrSID is protected by U.S. Patent No. 5,710,835.
Foreign Patents Pending. Unauthorized use or duplication prohibited
This readme file contains important information about MapObjects 2.3.

Contents
1.0

2.0
3.0

Installing MapObjects 2.3

1.1
How to install
1.2
System Requirements
1.3
MapObjects SDK for .NET requirements
1.4
Files installed in the MapObjects2 folder
1.5
Files installed in the ESRI Common Files folder
1.6
Files installed in the Windows Fonts folder
1.7
Files installed in the System folder
1.8
Folders Installed
What's New in MapObjects 2.3
Known Issues

1.0 Installing MapObjects 2.3

IMPORTANT NOTE: Installing MapObjects 2.3 will overwrite any existing installations of
MapObjects 2.x including MapObjects 2.2. MapObjects 2.3 supersedes any MapObjects
2.2 service packs, since all of the issues addressed in any MapObjects 2.2 service packs
are included in MapObjects 2.3.
Version checking is done so only those files that are older will be overwritten. The
installation will detect if there is already a more recent version of MapObjects installed
and if so a warning will be given and the install process will be aborted.

1.1 How to install

To install MapObjects 2.3, run the Mo23Setup.exe file located in the root folder of the
installation media. During installation you may choose to install any or all of the optional
components, such as Core Program files, Data Source support files and On-line help
files.
MapObjects 2.3 does not require a previous installation of MapObjects.

MapObjects should be installed from a user account which has administrative privileges
IMPORTANT: Before running the Setup program, close all unnecessary applications.
Make sure that all development environments or applications that use MapObjects are
closed before running the Setup program. (This will help you to avoid the requirement for
a system reboot when the installation is complete).

1.2 System Requirements

The recommended system requirements are as follows:

PC with Pentium class processor (Pentium 90 or higher recommended)

32 MB Ram (48 MB Ram or more recommended)

VGA or higher resolution monitor (Graphics card required)

Hard Disk Space approx. 203Mb with full install including the following:
MapObjects2 Folder - 103 Mb
System - 15Mb
Common Files - 82Mb
MS_Shared - 3Mb

Microsoft Windows 2000 or later operating system, with the latest service pack
and updates. See the Microsoft website for more information about the Windows Product
Lifecycle dates:
http://support.microsoft.com/default.aspx?scid=fh;[ln];LifeWin

1.3 MapObjects SDK for .NET requirements

The MapObjects 2.3 SDK for .NET is dependant upon the Microsoft .NET Framework and
the Microsoft .NET Framework SDK. If these components are not installed on your
machine, you can download them from the Microsoft website; they are available as
separate components.
By default, MapObjects will work with the Microsoft Framework and its SDK version 1.0,
which is supported on Windows 2000 and later, with the appropriate service packs and
updates. You can find more information about the system requirements for the framework
on the Microsoft website.
http://msdn.microsoft.com/netframework/previous/v1.0/default.aspx
However, if only version 1.1 if the .NET Framework and .NET Framework SDK is present,
you will still be able to use the MapObjects SDK for .NET. It is possible that later versions
of the .NET Framework will work similarly with MapObjects; however this is subject to the
exact details of future releases of the .NET Framework.
The MapObjects installation program will be able to detect the location of both the version
1.0 and 1.1 of the Framework and SDK. If you install MapObjects 2.3 to a version of
the .NET Framework later than 1.1, you will be given the opportunity during the install to
locate the Framework yourself, so that the MapObjects SDK for .NET can be installed. In
this case, you will need to locate the folder containing the Gacutil.exe file, which is part of
the .NET Framework SDK. In versions 1.0 and 1.1 of the .NET Framework SDK,
Gacutil.exe can be found in:
\<Microsoft Visual Studio .NET install folder>\SDK\<version number>\Bin
However, Microsoft may change this location in future versions, in which case you can
search manually for the Gacutil.exe file.

When you install the MapObjects SDK for .NET, you will be given the option to install
MapObjects help files for Visual Studio .NET; these help files will then be available within
the current version of Microsoft Visual Studio .NET on your computer.

1.4 Files installed in the MapObjects2 folder

The following files are installed in the MapObjects2 folder. By default, this will be
<MainDrive>\Program Files\ESRI\MapObjects2, however you will be prompted at install
time to change this if you wish.
File
MapObjects2.hlp
MapObjects2.cnt
MifShape.hlp
MifShape.cnt
MoMemTable.hlp
MoMemTable.cnt
MoSamples.hlp
MoSamples.cnt
Weblink.hlp
Weblink.cnt
ReadMeMO23.doc
Developer Connection.url
MifShape.bat
MifShape.exe
MifShape.pif
MO20.log
Register In Menu.reg
RegSvr32.exe

Version
-

Comments
MapObjects2 help file
MapObjects2 help TOC file
MifShape Converter help file
MifShape Converter help TOC file
MemTable help file
MemTable help TOC file
MapObjects2 samples help file
MapObjects2 samples help TOC file
Weblink help file
Weblink help TOC file

This readme file

Link to MapObjects Developer web
page
MifShape Converter batch file
MifShape Converter executable file
MifShape Converter pif file
MapObjects2 Install log
Registration Utility Registry file
Registration Executable file

5.0.1641.1

Additionally if the 'MapObjects SDK for .Net' option is selected, then a 'DotNet' folder will
be created below MapObjects2 folder, e.g. C:\Program Files\ESRI\MapObjects2\DotNet\.
Within this folder will be an 'Assemblies' sub folder containing the 3 .NET assembly files
listed in the table below.
Note: The MapObjects 2.3 SDK for .NET is dependant upon the Microsoft .NET
Framework and the Microsoft .NET Framework SDK. See section 1.3.
File
Version
Comments
ESRI.MapObjects2.Control.dll
2.2.1.0
Map Control Assembly
ESRI.MapObjects2.Core.dll
2.2.1.0
Map Objects Assembly
ESRI.MapObjects2.Custom.dll
2.2.1.0
Custom Objects Assembly
ESRI.MapObjects2.MemTable.dll
2.2.1.0
MemTable Assembly
(Note: These files are unchanged since MapObjects version 2.2).
All of these files have also been copied to and registered with the GAC. Please refer to
the section on "MapObjects and .NET" below for more information.
If you choose to install the MapObjects SDK for .NET help files for Microsoft Visual Studio
.NET, these help files will also installed in a sub-folder of the MapObjects DotNet folder,
named 'Help'. For example, C:\Program Files\ESRI\MapObjects\DotNet\Help.
In addition to the files and folders listed here and in section 1.8, a number of sub-folders
of the main MapObjects2 are created by the install. These folders will contain samples,

documentation, the Runtime installation, and other supporting files associated with
MapObjects 2.3.

1.5 Files installed in the ESRI Common Files folder

The following files are now installed in an ESRI sub-folder of the Windows Common Files
folder, if all options are selected during the install. For example, C:\Program
Files\Common Files\ESRI. This allows other ESRI and third party applications to share
these files.
File
Mo20.ocx
MO20.lic
AF20.dll
AFCust20.tlb
Mtch.dll
pe81.dll
sg81.dll

Version
2.3.1.0
2.3.1.0
8.1.0.631
8.1.2.667
8.1.2.667

Comments
MapObjects2 ActiveX Control
MapObjects2 License Info
MapObjects support library
AF20 custom type library
Address Matching support library
projection support library
shape geometry support library

Cad20.dll
Cade.DLL
Cadpi.DLL
Coverage20.dll
EDGE32.dll
MoSde302.dll
mosde80.dll
mosde81.dll
mosde82.dll
mosde83.dll
mosde90.dll
pe.dll
pe80.dll
pe82.dll
pe83.dll
pe90.dll
sde30.dll
sde80.dll
sde81.dll
sde82.dll
sde83.dll
sde90.dll
sg.dll
sg80.dll
sg82.dll
sg83.dll
sg90.dll
Shape20.dll
Street20.dll
Vpf20.dll

2.3.1.0
2.3.1.0
2.1.4.0
2.3.1.0
2.1.0.2
2.3.1.0
2.3.1.0
2.3.1.0
2.3.1.0
4.0.0.0
8.0.1.0
8.2.0.697
8.3.0.800
9.0.0.535
3.0.2.1
8.0.1.0
8.1.2.667
8.3.0.700
8.3.0.800
9.0.0.535
3.0.2.1
8.0.1.0
8.3.0.700
8.3.0.800
9.0.0.535
2.3.1.0
2.3.1.0
2.3.1.0

CAD support library

CAD support library
CAD support library
Coverage support library
StreetMap support library
SDE 3.0 support library
SDE 8.0 support library
SDE 8.1 support library
SDE 8.2 support library
SDE 8.3 support library
SDE 9.0 support library
SDE 3.0 client library
SDE 8.0 client library
SDE 8.2 client library
SDE 8.3 client library
SDE 9.0 client library
SDE 3.0 client library
SDE 8.0 client library
SDE 8.1 client library
SDE 8.2 client library
SDE 8.3 client library
SDE 9.0 client library
SDE 3.0 client library
SDE 8.0 client library
SDE 8.2 client library
SDE 8.3 client library
SDE 9.0 client library
Shapefile support library
StreetMap support library
VPF support library

AIImage20.dll
Dforrt.DLL
efileio.dll
elib.dll
ergxlib.dll
ethrlib.dll

2.3.1.0
6.0.612.101
8.3.1.0
-

Core Image support

Fortran Link Library
Core Image support
Core Image support
Core Image support
Core Image support

library
library
library
library
library

Iso8211.dll
libtiff.dll
mobase.dll
mofeat.dll
mogridio.dll
MoImageCat.dll
MoMrSID.dll

2.0.1.0
2.0.1.0
2.0.1.0
2.3.1.0
2.3.1.0

Core Image support library

Core Image support library
Core Image support library
Core Image support library
Core Image support library
Image Catalog support library
MrSID Image support library

AdoTable20.dll
InfoTable20.dll
JetTable20.dll
OdbcTbl20.dll
MemTable21.dll
MemTableServer.dll

2.3.1.0
2.3.1.0
2.3.1.0
2.3.1.0
2.3.1.0
2.3.1.0

ADO Table support library

INFO Table support library
Jet Table support library
ODBC Table support library
MemTable Table support library
MemTable Table support library

Weblink.ocx
Weblink.lic

2.1.1.1
-

MapObjects IMS Support

MapObjects IMS License Info

MO21Legend.ocx
MO21ScaleBar.ocx

2.1.0.1
2.1.0.2

MapObjects Legend Helper Component

MapObjects Scalebar Helper Component

The files listed below are also installed in the ESRI Common Files folder if the ArcSDE
Direct Connect option is selected during the installation process.
File
sdeora8isrvr81.dll
sdeora8isrvr82.dll
sdeora9isrvr82.dll

Version
8.1.2.667
8.3.0.700
8.3.0.700

Comments
Oracle8i Direct Connect Server
Oracle8i Direct Connect Server
Oracle9i Direct Connect Server

sdesqlsrvr82.dll
sdesqlsrvr81.dll

8.2.0.700
8.1.2.667

SQL Server Direct Connect Server

SQL Server Direct Connect Server

If the 'ArcSDE Direct Connect' option is selected during the installation process, the files
listed below are installed in a sub-folder of the ESRI Common Files folder named 'Bin'.
For example, C:\Program Files\Common Files\ESRI\Bin.
File
bin\gsrvrora8i81.dll
bin\gsrvrora8i82.dll
bin\sdeora8isrvr83.dll
bin\gsrvrora8i83.dll
bin\sdeora8isrvr90.dll
bin\gsrvrora8i90.dll

Version
8.1.2.667
8.3.0.700
8.3.0.800
8.3.0.800
9.0.0.535
9.0.0.535

Comments
Oracle8i Direct
Oracle8i Direct
Oracle8i Direct
Oracle8i Direct
Oracle8i Direct
Oracle8i Direct

Connect GeoServer
Connect GeoServer
Connect Server
Connect GeoServer
Connect Server
Connect GeoServer

bin\gsrvrora9i82.dll
bin\sdeora9isrvr83.dll
bin\gsrvrora9i83.dll
bin\sdeora9isrvr90.dll
bin\gsrvrora9i90.dll

8.3.0.700
8.3.0.800
8.3.0.800
9.0.0.535
9.0.0.535

Oracle9i
Oracle9i
Oracle9i
Oracle9i
Oracle9i

Connect GeoServer
Connect Server
Connect GeoServer
Connect Server
Connect GeoServer

bin\gsrvrsql81.dll
bin\gsrvrsql82.dll
bin\sdesqlsrvr83.dll
bin\gsrvrsql83.dll
bin\sdesqlsrvr90.dll
bin\gsrvrsql90.dll

8.1.2.667
8.2.0.700
8.3.0.800
8.3.0.800
9.0.0.535
9.0.0.535

SQL Server
SQL Server
SQL Server
SQL Server
SQL Server
SQL Server

Direct
Direct
Direct
Direct
Direct

Direct
Direct
Direct
Direct
Direct
Direct

Connect GeoServer
Connect GeoServer
Connect Server
Connect GeoServer
Connect Server
Connect GeoServer

bin\sdeinfsrvr90.dll
bin\gsrvrinf90.dll

9.0.0.535
9.0.0.535

Informix Direct Connect Server

Informix Direct Connect GeoServer

bin\sdedb2srvr90.dll
bin\gsrvrdb290.dll

9.0.0.535
9.0.0.535

DB2 Direct Connect Server

DB2 Direct Connect GeoServer

If the 'ArcSDE Direct Connect' option is selected, then the files listed below are also
installed, in a sub-folder of the MapObjects2 folder named 'Direct Connect'. For example,
C:\Program Files\ESRI\MapObjects2\Direct Connect\.
File
MO23_DirectConnect.doc

Comments
ReadMe for Direct Connect

1.6 Files installed in the Windows Fonts folder

MapObjects 2.3 installs the true type font files listed below in your Windows Fonts folder.
These files are not essential, but may be required to run the samples, and may also be
useful when creating new applications.
File
esri_1.ttf
esri_2.ttf
esri_3.ttf
esri_4.ttf
esri_5.ttf
esri_6.ttf
esri_7.ttf
esri_8.ttf
esri_9.ttf

Comments
ESRI Cartography font
ESRI Environmental & Icons font
ESRI Geometric Symbols font
ESRI Oil, Gas, & Water font
ESRI Weather font
ESRI Transportation & Municipal font
ESRI Geology font
ESRI Crime Analysis font
ESRI Transportation & Civic font

1.7 Files installed in the System folder

MapObjects 2.3 installs the files listed below in your system folder. These are
dependencies of the files which are installed into the ESRI Common Files folder and as
such are always installed unless the required version or a later version is already present.
File
Version
Ctl3d32.dll
mfc42.dll
Msvcirt.dll
Msvcp60.dll
msvcrt.dll
Msvcrt40.dll
oleaut32.dll
olepro32.dll
stdole2.tlb

Comments
2.31.0.0
6.0.8665.0
6.0.8168.0
6.0.8168.0
6.0.8797.0
4.22.0.0
2.40.4514.1
5.0.4514.1
2.40.4277.1

Microsoft Dynamic Link Library

Microsoft Dynamic Link Library
Microsoft Dynamic Link Library
Microsoft Dynamic Link Library
Microsoft Dynamic Link Library
Microsoft Dynamic Link Library
Microsoft Dynamic Link Library
Microsoft Dynamic Link Library
Microsoft Type Library

The file listed below is also installed in your system folder if either the MOIMS or
MapObjects Helper Components option is selected during the installation process.
File
Msvbvm60.dll

Version
6.0.88.77

Comments
Microsoft Dynamic Link Library

Additionally the file listed below is installed in your system folder if the MOIMS option is
selected during the installation process.
File
imsutil.dll

Version
1.0.0.14

Comments
ESRI Web Utilities

1.8 Folders Installed

The following folders and their contents are optionally installed into the Common
Files\ESRI folder:
Folder
CodePage
MO_Image
PE_Grids
Bin

Comments
Code Page Support (Coverages and INFO files)
ERDAS Imagine Image Support
NADCON, HARN and NTv2 Transformation Support (for projections)
As described above for the direct connect files

The following folder and its contents are optionally installed in the MapObjects2 folder, as
described above in section 1.3:
Folder
Georules

Comments
Geocoding Support (Matching and standardizing rule files)

2.0 What's New in MapObjects 2.3

MapObjects 2.3 includes numerous fixes and enhancements.
Added support for final ArcSDE 9.0 as a client, and for direct connect
MapObjects now supports ArcSDE 9.0, both as an ArcSDE client, and a direct connect
client for Oracle 8i/9i and SQL Server databases. Informix and DB2 databases are also
supported as 9.0 direct connect clients.
The supporting files for direct connect installed by MapObjects have changed since
version 2.2; the direct connect readme details all the required information. Server setup is
now performed from the ArcSDE post install steps.
The MapObjects 2.3 Runtime Installation includes these new client libraries.
Include all address styles available with ArcGIS 9 into MO 2.3
MO 2.3 now uses the new ArcGIS 9 style geocoding rules. Existing .dct, .stn, .pat, and
.cls files have also been updated - note that existing .mat files have not been replaced
with the ArcGIS 9 files, as the match variable names in the ArcGIS 9 georules were
different, and therefore may have caused backward compatibility problems with variable
names hardcoded in MapObjects applications.
New address styles were also added - see the MapObjects help files for full information.
The Streetmap geocoding files (stmap.*) have not been updated as MapObjects does not
support the new SDC format streetmap data for which the ArcGIS 9 streetmap geocoding
rules were created.

Data and Maps CDs have been updated

The Data and Maps CD-ROM and DVD set which accompanies MapObjects has been
updated.
The new data has a different structure to the data on the previous Data and Maps set,
therefore you may need to update your application if it uses hard-coded paths to access
data, particularly the StreetMap data sets. See the Visual Basic 6 StreetMap sample for
an example of accessing the new StreetMap data.
Fix MapObjects 2.2 Install with VS.NET 2003
The MapObjects SDK for .NET requires the Microsoft .NET Framework SDK to be
installed. The .NET Framework SDK is installed as part of Visual Studio .NET. Since the
previous release of MapObjects (2.2), a second version of the .NET Framework and .NET
Framework SDK has been released (version 1.1). If an attempt was made to install
MapObjects onto a machine with only this later version of the .NET Framework SDK, the
option to install the MapObjects SDK for .NET would be unavailable.
In MapObjects 2.3, both versions 1.0 and 1.1 of the .NET Framework SDK will
automatically be detected by the MapObjects installation. Also, potential later versions of
the SDK can be manually located by the user, during the installation.
In addition, the MapObjects 2.3 Runtime Installation now takes an additional command
line parameter, allowing you to specify the location of future versions of the .NET
Framework (versions 1.0 and 1.1 will again be automatically detected by the runtime).
LabelPlacer not supported for Multipoint MapLayers
MapLayers containing multipoint shapes can now be labeled with the LabelPlacer. Each
point in a multipoint feature is labeled as an individual point (this behavior being the same
as found in ArcGIS).
MapObjects throws a non-specific error on OpenCatalog if image not found
For image catalogs which reference missing image files, an error is raised if a referenced
image file cannot be found during the OpenCatalog method. The error message will now
include the name of the image which is missing. You should ensure that the Image
Catalog support option is selected during the install of MapObjects 2.3 if you are installing
over an existing MapObjects 2.x installation to ensure you receive this fix. File existence
checks have also been optimized, resulting in faster execution times for the OpenCatalog
method.
Export using with empty CoordinateSystem parameter causes automation error
Previously, if the Export method of the Recordset object was called by passing a null
value as the optional CoordinateSystem parameter, this would cause a non-specific
automation error. This case is now treated as if the parameter were missing.
Update MapObjects2.h file for TrackingLayerDraw Constants
MapObjects VC++ sample applications have been updated to include the
TrackingLayerDraw Constants in the MapObjects.h header file.
Getting the TableDesc of a Recordset after or during an edit operation gives errors

Previously, attempting to access the TableDesc of a Recordset object after or during an

edit may have caused an error, resulting in the in-memory representation of the shapefile
being corrupted (the data on disk would be left unchanged), requiring a restart of the
application..
This situation is now resolved, and the TableDesc an be accessed; however during an
update the CodePage property may return the default value, regardless of the actual
CodePage of the data.
Unable to display some line features in DXF files correctly
Previously, displaying some DXF files may result in incorrect line features being
displayed, characterized by diagonal or straight lines over the extent of the layer.
128 character length limit in ImageLayer objects File property
The ImageLayer object now supports file paths of up to 256 characters for the File
property. Note that the Grid image format in particular does not support file paths longer
than 128 characters.
Some ArcSDE layers disappear at half of the map full extent
Zooming in to a map which contained SDE layers, particularly at the edges of the Extent
of a MapLayer, may previously have resulted in the layers features disappearing.
AddRelate broken when used on a DataConnection object using ArcSDE
instance=port:5153 syntax
This issue affected DataConnection objects which had a Database property using syntax
of the type instance=port:5153. In this case, an attempt to create a join to another
ArcSDE Table by using AddRelate would have applied an incorrect join type, which would
have resulted in an incorrect Recordset.
BMP would crash MO application
In some cases, MapObjects would have attempted to interpret a BMP image file as a
NITF (CADRG) image file, causing a crash.
Removed ERDAS tiff.dll to avoid dll dependency issue
The Tiff.dll file, which was installed by previous versions of MapObjects to the
MO_IMAGE\Devices\NTx86 folder, is no longer required by MapObjects, and is not
installed by MapObjects 2.3 or the MapObjects 2.3 Runtime Installation.
Pressing Alt-Tab repeatedly while MapObjects is drawing causes a crash
Previously, pressing the Alt and Tab keys to switch between applications while
MapObjects was performing drawing operations may crash the MapObjects application.
This issue is now resolved, and in addition, the fix allows you to place breakpoints in
MapObjects drawing events when debugging your application.
Sometimes the size of font glyphs changes by a pixel
The LabelPlacer object converts its label heights from the font size to map units, in order
to perform label conflict resolution in map units. Previously, during this conversion the
display height of the text may have changed by a pixel in height.

Problem reading CADRG files

CADRG files containing pixels values out of their valid range may previously cause the
MapObjects application to crash, or to display the image incorrectly or not at all.
Black horizontal bar when displaying TIFF: 6.0, Packbits, Tiled
For Tiff 6.0 format images with packbits and tiled, a black horizontal bar may have been
displayed at the bottom edge of the image.
Deleting a record from a shape file with large precision will corrupt the attributes
Previously, using MapObjects 2.2 to delete records from a shapefile containing Fields with
a FieldPrecision greater than the maximum allowable by MapObjects (19) could corrupt
the attribute table of the data set, during the dataset compaction routines.
Performance issue on getting type of GeoCoordSys/ProjCoordSys objects in MO22
Previously, when GetType was called on a coord sys object, the Projection Engine was
queried each time for the value, which is a time consuming function. GetType now stores
the type value.
MakeExtentFromXYScale has bad example for scale from precision
The MapObjects 2.2 help files contained incorrect example code for the geometry
methods optional rectangle parameter calculation. If you made use of this code in your
application, you should ensure your code is updated from the MapObjects 2.3 example
code.
A number of other more minor software and documentation issues have also been
corrected in MapObjects 2.3.

3.0 Known Issues

The following are currently known issues in this version of MapObjects.
ArcSDE 9.0 Coordinate systems not supported by MapObjects
If you try to view a shapefile which has an accompanying .prj file which uses a coordinate
system element (Projection, Unit, Datum, Spheroid, PrimeMeridian or
GeoTransformation) which is available in the 9.0 version of the projection engine library
(part of ArcGIS 9.0) but which is not included in previous versions of the projection
engine, then MapObjects will not be able to display the file. Adding the layer via the
property page will result in the error "Cannot display file. File Invalid.", and the layer will
not be added to the map control. If you attempt to add the layer programmatically, the
result from FindGeoDataset will be null.
To add such a layer to MapObjects, you could remove the prj file in order to display the
data unprojected in MapObjects. Alternatively, you could re-project the data to a
compatible system, using the software with which you originally created the data.
MrSid writeable extent does not change images location

If you try and change the Extent property of a MrSid image it will not override the images
georeference information, and the image will appear clipped (other image formats will
refresh and appear in the new extent).
To workaround this issue, the world file (.sdw) can be rewritten to change the
georeference information of the MrSid image. The image must be reloaded if the world
file is changed.

EOF