Mapxtreme V7.2.0 Release Notes: List of Topics
Mapxtreme V7.2.0 Release Notes: List of Topics
Mapxtreme V7.2.0 Release Notes: List of Topics
0
Release Notes
United States:
Sales: 800.327.8627
www.pb.com/software
Canada:
Sales: 800.268.3282
www.pb.com/software
Europe/United Kingdom:
Phone: +44.(0) 149 416 600
www.pitneybowes.co.uk/software
Asia Pacific/Australia:
Phone: +61.2.9437.6255
www.pitneybowes.com.au/software
2013 Pitney Bowes Software, Inc. All
rights reserved.Pitney Bowes Software
Inc. is a wholly-owned subsidiary of
Pitney Bowes Inc. Pitney Bowes, the
Corporate logo, MapInfo, Group 1
Software, and MapXtreme are
[registered] trademarks of Pitney Bowes
Inc. or a subsidiary. All other trademarks
are the property of their respective
owners.
March 21, 2014
PDF version accessible from the Start > All Programs menu under MapInfo >
MapXtreme 7.2.0 > Learning Resources browser
PDFversion on the Pitney Bowes Software Inc. website
List of Topics:
Whats New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Bug Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Supported Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation Guidance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performance Recommendation . . . . . . . . . . . . . . . . . . . . . . . .
2
2
3
5
6
7
Whats New
Whats New
MapXtreme includes the following new features in version 7.2.0.
ECW
TableFileAccessErrorEvent
There is a new exception event TableFileAccessErrorEvent that can be used for MWS file loading error handling
when an MWS file contains a reference to invalid file paths.
EPSG 3111, EPSG 5845, 5846, 5847, 5848, 5849, 5850, 5851, 5852, 5853, 5854, 5855, 5856 and 5857
SIRGAS 2000 (EPSG 31965 - EPSG 31988)
Extended Transverse Mercator (Extended TM Zone 1, Northern Hemisphere (WGS 84) to Extended TM Zone 60,
Southern Hemisphere (WGS 84))
Bug Fixes
The following issues were resolved in this release.
WMS
ModifyRangedThemeSettings control loses the appropriate count assigned to each Custom range when the
number of ranges are increased.
MapXtreme 7.1 and MapXtreme 7.0: Memory leak encountered when repositioning map, especially when working
with aerial images.
Memory Leak in MapXtreme 7.1 while trying to create ranged theme based upon Quantile method.
Fix the range formatting in the 'Modify Range Theme' dialog Styles tab.
Zoom and pan on a TIFF image causes drawing error at Mapinfo.GeoObjectDocWrapper.mDrawDoc.
Known Issues
Oracle
Performance
Coordinate Systems
Known Issues
Installing MapXtreme 7.1 and 7.2 together:
Leadtools dll's are same for both versions so uninstalling one may corrupt the other installation for Leadtools.
In Visual Studio 2010 two controls with the same name cannot be activated at the same time. If you want to use the
controls from previous version then you must disable the latest control first.
Project templates provided by MapXtreme 7.1 installation, when used, include the latest references of MapXtreme
7.2 dll's in the project. User has to remove the 7.2 references and re-add the references from MapXtreme 7.1 dll's.
MILicensingService renamed to MILicensingService72.exe for MapXtreme 7.2. If target machine has both
MapXtreme 7.1 and 7.2, then there will be two MILicensingService running.
OGC Compliancy failures: MapXtreme 7.2 OGC compliancy is incomplete due to issues with the OGC site. Issues
have been raised with OGC and once those are fixed then MapXtreme will test for OGC compliancy.
64-bit Applications on Visual Studio 2010 and Visual Studio 2012 Development Server. Visual Studio 2010 and
Visual Studio 2012 do not support running 64-bit web applications in Development Server. An incorrect format
exception is returned when running trying to run 64 bit applications.
Merge Modules additional requirements: If you are creating your own installer with our merge modules (not
available in the Trial versions), you must add the following prerequisites: .NET Framework 4.0 (not the client profile),
MSXML 6.0 and Visual C++ 10.0 CRT (x86 and x64) and Visual C++ 12.0 CRT (x86 and x64). x86 is needed for both
x86 and x64 apps.
Column Named NOT: There is a MapXtreme issue parsing SQL statements containing columns named 'NOT'.
GRD and GRC Limitations: MapXtreme 64-bit cannot open .GRD and .GRC files without a .TAB file. If .TAB is
present these files are opened as rasters only using the vmgrid.rhl. They will not be opened as grid files. This does not
apply to 32-bit MapXtreme.
Re-projecting palate-based images with 256 colors: When image re-projection of a raster is turned on, it displays in
MapXtreme with a black border. The workaround for this issue is to convert the image to non-palette based or reduce
the image colors to below 256.
Raster/Grid Handlers and Oracle: MapXtreme may be unable to load some raster and grid handlers when the Oracle
client is installed. This can occur when running a 32-bit MapXtreme application, such as Workspace Manager on either
a 32-bit or 64-bit operating system. To work around this issue, add C:\Program Files (x86)\Common
Files\MapInfo\MapXtreme\7.x.x\RasterGridHandlers to the beginning of your system PATH variable.
Oracle Arcs and Circles: When MapXtreme reads Oracle arcs or circles, they are converted to a polygon
representing the arc or circle. The resolution (# of points) defaults to 40, up from 20 prior to this release. You can
specify a different number of nodes in your app.config or web.config by adding the following:
<configuration>
<appSettings>
Known Issues
TimeToString
Converts a time into a string.
Syntax
TimeToString ( time, fmt)
Arguments
time is a time.
fmt is a string identifying the format of time.
Remarks
TimeToString does not work with DateTime values.
ACE Drivers for Microsoft Access on 64-bit: The MS Access Database Engine contains components that facilitate
the transfer of data between MS Office applications and non-Office applications. MapXtreme does not provide this
redistributable. See http://www.microsoft.com/en-us/download/details.aspx?id=13255 for usage, limitations. On
32-bit applications you can continue to use the Jet driver which may perform better in multi-thread mode.
Running .NET Framework 2 application on 64-bit Windows: When using the grant set <trust level="Full"
legacyCasModel="true" />, an error message Loading this assembly would produce a different grant set from other
instances is presented when you run a .NET Framework 2.0-based application on a computer that is running a 64-bit
version of Windows. See http://support.microsoft.com/kb/2282372.
.NET Framework 4 Client Profile: MapXtreme does not support the .NET Framework 4 Client Profile. For more
information see http://msdn.microsoft.com/en-us/library/cc656912.aspx.
Supported Environments
Supported Environments
Pitney Bowes Software Inc.has tested and supports MapXtreme on the following.
Operating Systems
Windows 8 (x64)
Windows 7 (x86, x64)
Windows Vista with SP2 (x86 , x64)
Windows Server 2012 (x64)
Windows Server 2008 R2 (x64)
Windows Server 2008 with SP2 (x86 , x64)
Windows Server 2003 R2 with SP2 (x86 , x64)
Windows Server 2003 with SP2 (x86 , x64)
Windows XP with SP3 (x86 , x64)
Architecture
64-bit
32-bit
Browsers
Support *
Supported databases
Recommended development environments (IDE). Others can be used, however, the MapXtreme installer will
not integrate its templates, samples, and help system.
**
The MapXtreme Learning Resources displays in Internet Explorer automatically, regardless of your default
browser setting. This will not change your default browser setting.
MapXtreme does not support the Express Editions of Microsoft Visual Studio.
Installation Guidance
Processor
Video Card
Installation Guidance
Installer: We recommend using the x64 installers on x64 platforms; even if your application is x86. The x64 installers
will install the features/components needed for x86 development and runtimes. Currently we do not support having two
versions of our installations. For example if you have version 7.2.0 install and want to use the x64 version, you have to
uninstall the x86 version, followed by installing the x64 version.
Installer - Run As Administrator: When installing MapXtreme on Windows 7, Windows 2008 Server and Vista, be
sure that you specifically choose Run As Administrator from the shortcut menu. You must also be an administrator on
the installation target.
Run Visual Studio as Administrator: Be sure that you are running Visual Studio as administrator for full privileges in
the development environment.
How to Register MapInfo.CoreEngine in COM+:
Installing MapXtreme (x64) creates two COM+ applications - x86 and x64. If both objects (via Component Services)
are not present, run the following commands in the specified given:
C:\WINDOWS\Microsoft.NET\Framework64\v4.0.30319\REGSVCS.EXE /u /quiet
C:\WINDOWS\Microsoft.NET\assembly\GAC_64\MapInfo.CoreEngine\v4.0_7.2.0.64__
93e298a0f6b95eb1\MapInfo.CoreEngine.dll
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\REGSVCS.EXE /u /quiet
C:\WINDOWS\Microsoft.NET\assembly\GAC_32\MapInfo.CoreEngine\v4.0_7.2.0.64__
93e298a0f6b95eb1\MapInfo.CoreEngine.dll
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\REGSVCS.EXE /quiet /noreconfig
C:\WINDOWS\Microsoft.NET\assembly\GAC_32\MapInfo.CoreEngine\v4.0_7.2.0.64__
93e298a0f6b95eb1\MapInfo.CoreEngine.dll
C:\WINDOWS\Microsoft.NET\Framework64\v4.0.30319\REGSVCS.EXE /quiet /noreconfig
C:\WINDOWS\Microsoft.NET\assembly\GAC_64\MapInfo.CoreEngine\v4.0_7.2.0.64__
93e298a0f6b95eb1\MapInfo.CoreEngine.dll
Performance Recommendation
MapXtreme Help Integration: If you have removed the MapXtreme Developer Reference from Visual Studio, set your
Help Viewer to use local help and then manually integrate the Developer Reference following the procedure below for
your version of Visual Studio:
Visual Studio 2012
1. Choose Help > Add or Remove Content.
2. In the Manage Content tab, navigate to the HelpContentSetup.msha. The MapXtreme Developer Reference will
display in the list.
3. Click Add, then the Update button to integrate it.
4. At the Security dialog, click Yes to proceed.
Visual Studio 2010
1. From the Help > Manage Help Settings in Visual Studio, choose Install Content from Disk.
2. Navigate to the Help\Documentation folder under your MapXtreme installation. Select HelpContentSetup.msha and
click Open, then Next.
3. Under the Actions column for MapXtreme Developer Reference 7.2.0, click Add, then click the Update button.
4. At the Security dialog, click Yes to proceed.
5. At the conclusion of the update, click Finish. Click Exit to leave the Help Library Manager.
Performance Recommendation
SQLServer 2008 key selects and MIDataReader performance: When creating an MIDataReader from a SQL
command statement built on a key select, we recommend using the pseudo key column name MI_KEY in the
MapXtreme select statements, regardless of the real column name.
MapXtreme interrogates the SQLServer2008 table schema to determine the key, based available information, such as:
PRIMARY KEY index
IDENTITY column
UNIQUE identifier
MI_PRINX column name.
This evaluated key is interpreted as "MI_KEY"
Since MapXtreme's SQL key SELECT behavior is optimized for MI_KEY use, we recommend that you use MI_KEY in
your MapXtreme select statements, regardless of the real column name.
For example, if the table is defined with a PrimaryKey column 'MI_PRINX', the MIDataReader command should
nonetheless reference MI_KEY for key select statements, otherwise,MapXtreme's SELECT behavior doesn't make
use of the evaluated key column, so it potentially skips around the key select optimization.
In this example scenario, where MI_PRINX is defined as the key column, the following select statement exhibits
performance issues over a large data set:
SELECT * from linkar WHERE MI_PRINX in (22924,22925,22926,22927,22928)
Whereas the following statement utilizes the key select to advantage to get acceptable performance, using the
MapXtreme pseudo key column name, MI_KEY:
SELECT * from linkar WHERE MI_KEY in ('22924','22925','22926','22927','22928')
Note, MI_KEY is evaluated as a string during the select statement parsing, so you need to enclose the values in '''
marks.