MapDotNet UX Help

Choose Your Technology Path

Developing Rich Interactive Mapping (RIM) applications with MapDotNet UX has never been easier. To do so you must first choose your technology path:

HTML5 Technology Path with the MapsJS Map Control

For mobile, consumer and touch-friendly mapping applications with rich interaction, MapsJS HTML5 map control plus the MapDotNet UX REST Services is the way to go!  The following components are required for developing your custom application:

  1. MapDotNet UX REST Web Services (if you intend to render custom maps or do any kind of spatial analysis)
    1. Must use basicHTTPBinding in WCF
    2. Requires a clientaccesspolicy.xml file added to the web root of your service if you intend to access services from an application server on another domain
  2. IIS web server website hosting your web services and HTML5 application
    1. Requires proxy.ashx inside of /clientbin folder (this is used to proxy calls to other third-party web services which do not have a client access policy - see sample Silverlight application)
  3. MapsJS HTML5 Map Control (available for download MapsJS.com or from the installer)
    1. isc.rim.js - required
    2. jquery-1.9.1.min.js - required

Microsoft Silverlight Technology Path

For web-based mapping applications with rich interaction, combining Microsoft Silverlight 5 and MapDotNet UX is recommended. You must have the proper Visual Studio add-ons for Silverlight 5 (Silverlight Tools and VS2012). The following components are required for developing your custom application:

  1. MapDotNet UX SOAP Web Services (if you intend to render custom maps or do any kind of spatial analysis)
    1. Must use basicHTTPBinding in WCF
    2. Requires a clientaccesspolicy.xml file added to the web root of your service if you intend to access services from an application server on another domain
  2. Microsoft ASP.net website hosting your Silverlight application (from within Visual Studio create a new Silverlight Web Application)
    1. Requires proxy.ashx inside of /clientbin folder (this is used to proxy calls to other third-party web services which do not have a client access policy - see sample Silverlight application)
    2. <asp:Silverlight ... Windowless="True" /> should be set on you Silverlight control.
  3. MapDotNet UX SDK Silverlight Libraries
    1. ISC.MapDotNetServer.CommonSL - required
    2. ISC.MapDotNetServer.CommonSL.Maps - required if you are requesting map images or rendering locally
    3. ISC.MapDotNetServer.CommonSL.Data - required for spatial analysis (query, transform) or data editing (insert, update, delete)
    4. ISC.RIM.Silverlight - required RIM control

Microsoft Windows Presentation Foundation (WPF) Technology Path

For all other non-web-based mapping applications with rich interaction, Microsoft Windows Presentation Foundation (WPF) [.NET Framework 4.5] and MapDotNet UX is recommended. The following components are required for developing your custom application:

  1. MapDotNet UX SOAP Web Services(if you intend to render custom maps or do any kind of spatial analysis)
    1. May use any of the supported endpoints (address, binding and channel) on WCF - basicHTTPBinding is the default used by all MapDotNet components
  2. MapDotNet UX SDK WPF Libraries
    1. ISC.MapDotNetServer.Common - required
    2. ISC.MapDotNetServer.Common.Maps - required if you are requesting map images or rendering locally
    3. ISC.MapDotNetServer.Common.Data - required for spatial analysis (query, transform) or data editing (insert, update, delete)
    4. ISC.RIM.WPF - required RIM control

Quick-start Steps for adding a Silverlight and WPF Map to solution