The ProviderTemplate tool allows you to build your own LocalNative provider against your specific version of MapGuide/AIMS NOTE: These instructions below assume the SDK directory structure is not modified. Do not change this directory structure or these instructions below may not work How to use the tool Run ProviderTemplate.exe Ensure the path to csc.exe is correct. On most windows installations, this is the case Ensure the path to your MapGuide .net assemblies is correct Set the MapGuide version to the major.minor.revision version of your MapGuide/AIMS server. This is included in the file name of the compiled assembly Set the MapGuide assembly type. The MapGuide .net API is either monolithic (a single MapGuideDotNetApi.dll) or modular (multiple OSGeo.MapGuide dlls). Versions of MapGuide Open Source before 2.2 (or MGE/AIMS 2011) are monolithic. Releases afterwards are modular. Optionally tick the Build Debug checkbox to build the LocalNative provider in debug mode Click the Build button to build the LocalNative provider assembly. The assembly will be in the Bin directory and the supporting dlls will be in the Lib\MapGuide directory. Copy the LocalNative provider assembly and its supporting dlls to your application's output directory. Edit the ConnectionProviders.xml file to include an entry for your LocalNative provider assembly. The name of the provider must be Maestro.LocalNative and the type must be OSGeo.MapGuide.MaestroAPI.LocalNativeConnection