[mapguide-users] Re: Again: strong naming of MapGuideDotNetApi.dll
Jackie Ng
jumpinjackie at gmail.com
Mon Oct 11 10:04:38 EDT 2010
The purpose of RFC68 is that if you're developing a new MapGuide application,
you only need to reference the specific OSGeo.MapGuide.*.dll assemblies you
actually need. You do not need to reference MapGuideDotNetApi.dll
For existing applications that reference the old MapGuideDotNetApi.dll, the
newer one just acts as a stub that points to the OSGeo.MapGuide.*.dlls. You
should not have to recompile your existing MapGuide applications in this
case.
MaestroAPI is built against a specific version of MapGuideDotNetApi.dll
(v2.0.0 I believe). The binding redirect trick is so you do not have to
recompile your application against the newer version of
MapGuideDotNetApi.dll
On second thought, this too may not even work for MGOS 2.2/MGE 2011,
especially if MaestroAPI uses APIs affected by RFC89
(http://trac.osgeo.org/mapguide/wiki/MapGuideRfc89). I'll have to double
check this.
- Jackie
--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/Again-strong-naming-of-MapGuideDotNetApi-dll-tp5622823p5623239.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
More information about the mapguide-users
mailing list