I believe I have found a solution for this. The short story is that signer.exe doesn't handle the unique scenario imposed by the MGOS2.2/MGE2011 assemblies being split up. It involves using ildasm.exe and ilasm.exe to manually sign these assemblies, and a little IL hackery is required to ensure that MapGuideDotNetApi.dll references the *signed* version of these assemblies.
I tested Maestro 2.1.4 in native TCP/IP mode with the strong-named versions of the MGOS 2.2 RC1 dlls, and it works! I'm currently documenting the process to do this. - Jackie -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/Again-strong-naming-of-MapGuideDotNetApi-dll-tp5622823p5633303.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
