MapDotNet Server 2007
Release Notes for Version 6.5
Release Date: 12/17/2007
Release notes contain important information available at the time of the Version 6.5. Please read this for information as to what changes have occurred since MapDotNet Server 2007 Version 6.1.2. Although the major version number was not incremented, there are many improvements from 6.1.2
Please note what's new in MapDotNet Server 6.5:
-
WCF services (replaces WSE3 services from 6.1.2)
-
Katmai (SQL Server 2008 public CTP) rendering, query and edit connectors
-
Oracle 10g and 11g rendering / query / edit and transforms
-
Server-side map caching
-
Log4Net profiling and event logging
-
Map renderer upgraded to MapServer 5.0
-
Virtual Earth 6.0 compatibility and shape support
-
Improvements to VE Template II for better error handling and diagnostics
-
Improved coordinate reference system (CRS) and query/edit/transform models
-
Native support for transforms not relying on underlying RDMS
-
Various other fixes and performance improvements
New Features
-
One of our biggest improvements in version 6.5 is our move to Microsoft’s WCF (Windows Communication Foundation). All of the web services provided in version 6.5 are now based on WCF To make the transition seamless, the MapControlBridge service proxies are now WCF clients simplifying the transition to 6.5 from prior versions of MapDotNet Server.
-
MapDotNet Server supports the November public CTP of SQL Server 2008 (codename Katmai) for rendering maps and tiles, spatial querying and editing. As SQL Server 2008 approaches release we will be following suit expecting support for the final in version 7.0 of MapDotNet Server.
-
In version 6.5 of MapDotNet Server we have added support for Oracle 10g and 11g. This is includes full support for map and tile rendering. Query, edit and transform support is supported with a couple minor caveats
-
A server-side map cache interface (IMapCacheManager) has been provided for developers to easily add caching to the map web service. For example, a tile cache can now be added on the services end of your solution as opposed to only the application side as in previous versions of MapDotNet Server. See an example provided on the support wiki for more information.
-
We have completely overhauled logging and profiling in MapDotNet Server 6.5. The “status log” in previous versions has been removed and has been replaced with Log4Net listeners on all services. You can set up your own log output format and use third-party tools to monitor the health and status of MapDotNet web services.
Enhancements
-
The MapServer based map renderer has been upgraded to version 5.0. MapServer 5.0 is a major release and includes several enhancements including support for the AGG renderer for excellent looking anti-aliased maps and tiles.
-
We have enhanced the Virtual Earth namespace in our SDK to support version 6.0. This includes support for shape z-indexing and altitude.
-
We have improved our VE Template II for Virtual Earth rapid application integration. Building a web-based application incorporating the Virtual Earth SDK, access to the MSDN servers, your own business tile server, access to your business spatial data, AJAX and ASP.NET all in one application opens up a lot of fault points and areas where developers can get stuck. We have added a diagnostic tool to our VEBase class which will run a series of tests to see where a problem resides. Place ?RunDiagnostics=true on your web application query string to return an XML report.
-
There have been multiple enhancements to our query / edit and transform connectors including support for transformations without going through the spatial RDMS.
Changes
The following is a list of changes from 6.1.2 and will require addressing in your application should you wish to upgrade it to version 6.5
Non-breaking changes (unusual cases may exist):
-
All status is now reported by Log4Net
-
Profiling is handled through Log4Net now
-
Moved Blob2SQL class from ISC.MapDotNetServer.Controls.VirtualEarth to ISC.MapDotNetServer.Common
-
Added WCF proxies to ISC.MapDotNetServer.Controls assembly
-
Added CacheServiceProxies bool property to MapControlBridge (default true) – maintains static versions of WCF proxies for improved performance. Set to false if the application must connect to other MDNS web services at runtime.
-
All MDNS VE Templates are updated to use WCF instead of WSE3 (see upgrade document for any breaking changes)
-
Added MDNMouseMove JS function to VEBase which if defined by the application is called and passed the current mouse position in lat/lon
Potential breaking changes:
-
Transform connector no longer looks at the mapfile metadata for connection type and connection string. The values are now passed in via the TransformRequest
-
Removed support for MapIDs in the web.config – only in MapFiles.xml and the Boolean flag to various calls to only fetch read-only mapIDs now checks actual file attributes for “read-only.”
-
The GetLayerByIndex web method has been removed from MapService as it was difficult to use and layers should be retrieved by ID.
-
MapControlBridge proxies all use WCF instead of WSE3 (breaking change if the proxies are accessed directly through your code)
-
PreServiceCall events in the MapControlBridge pass in an event argument with an attached WCF proxy instead of the WSE3 proxy
-
The WCF version of map services does not have GetCustomLegendIcon – only GetLegendIcon but request Xml may be null to provide this capability
-
The WCF MapService renamed “GetBaselineMapState” to “GetBaselineMapDescriptionState”
-
Version 6.5 moved application use of VEPConfig into VEMConfig (for the VE Map configuration). VEPConfig remains the same for the preloader. It was confusing to have VEPConfig used dual-purpose to both hold the VE map definition loaded from the map file and the preloader configuration
-
SetVEPConfig is no longer called by OnLoadComplete (SetVEMConfig is now called)
-
There is no longer any security context used at design-time (Visual Studio or Map File Generator) to access a WCF service (if you are developing, the client connects over a basicHttpBinding with no security). The login fields have been removed from the MapControlBridge designer. WCF allows for the security context to be defined by an administrator at deployment
-
QueryResultTable.ResultSetBoundsSerial is now returned as a serialized Envelope by all connectors
-
QueryResultRow.ShapeBoundsSerial is now returned as a serialized Envelope by all connectors.
-
Added web.config setting in admin services for path to MapFiles.xml and for Log4Net config file <add key="MapFilesXmlPath" value="C:\Projects\MapDotNetServer\MapDotNetServer Web Service\MapFiles.xml"/> <add key="Log4NetConfigPath" value="C:\Projects\MapDotNetServer\MapDotNetServer Web Service\Log4NetConfig.xml"/>
-
-
In QueryRequest, EditRequest, and TransformRequest, properties indicating buffer distances formerly had accompanying boolean properties indicating whether to apply the buffer. These have been removed and non-zero buffer distances now imply buffering.
See "Upgrading to 6.5" for more discussion of breaking changes.
Release Notes 6.1.2