This is sadly a leaky abstraction that is unavoidable at the moment. You have to be cognizant of the fact that although you're writing .net code, it is .net code that ultimately wraps and interops to native C/C++ code, so its memory management and lifecycle issues can crop up in your .net code if you write your code in a "too .net" fashion.
So, I'd extend Benoit's advice to say that you should be capturing to a variable *any method in the MapGuide API that returns an object reference*, not just methods that return MgByteReaders. - Jackie -- View this message in context: http://osgeo-org.1560.x6.nabble.com/30-seconds-delay-after-creating-100-CreateRuntimeMap-calls-tp5309691p5310221.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapguide-users
