I've changed how Maestro.LocalNative is setup post-4.0. It's now hard referenced against the version of MapGuide it supports (currently only MGOS 2.2 and 32-bit). I plan to include the LocalNative library project as part of the SDK so you can roll your own LocalNative connection assembly for your particular version of MapGuide/AIMS instead of going through this assembly binding redirection business.
One of these changes is changing the name of the implementation assembly so that you know what version of MapGuide the assembly is supposed to be used against. The implementation assembly has changed to OSGeo.MapGuide.MaestroAPI.Native32-2.2.0.dll As you can guess, it is for MGOS 2.2 and is 32-bit - Jackie -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/MaestroAPI-Can-t-use-LocalNative-Connection-from-API-in-trunk-tp7184159p7184213.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users