This page is part of the MapGuide Future section, where ideas are proposed and refined before being turned into RFCs (or discarded). Visit the Future page to view more!

Overview

Currently, MapGuide can be used with Microsoft .Net web applications through the use of the .Net APIs and manual HTML, JS, and other features via Fusion. This development model is less-than-intuitive for many .Net developers, and is really hindering the uptake of MapGuide by .Net shops.

Ideally, MapGuide would provide a series of custom Microsoft AJAX controls (see ​http://codeplex.com/AtlasControlToolkit for examples) that would allow the visual design of a Fusion application, including HTML and JavaScript and a back-end component that auto-generates an ApplicationDefinition.XML file.

Less ideally, MapGuide would provide a library parallel to Fusion that performs the same kind of function.