I also find the naming system quite confusing.
Generally, most map operations can take either a MapName or MapDefinition.
The MapName must sometimes be entered with either a full path, or the
map name.
Sometimes both works, sometimes only one works. I would personally
prefer only the full path.
I don't know which behavior would be classifed as "bugged", but I share
your confusion.
Regards, Kenneth, GEOGRAF A/S
Gunter Becker skrev:
OK I've found out how to change my code that this works again.
I had to open the map with the MapName not with the ResourceIdentifier:
MgMap map = new MgMap();
MgResourceIdentifier mapId = new MgResourceIdentifier("Session:" +
MgSessionId + @"//" + MapName + "." + MgResourceType.Map);
map.Open(ResourceService, MapName); // map.Open(ResourceService, mapId) -
That's wrong
But I'm still confused because I don't know what the difference is between
opening a runtime map with the ResourceIdentifier or the MapName. Until now
I supposed that these both methods have the same result. Maybe someone can
explain this behavior. Was it a bug in the former release of MapGuide or is
it one now?
Gunter
Kenneth, GEOGRAF A/S wrote:
Are you mixing som 1.1 and 1.2 API's ?
There were some changes to how the Layers are stored in 1.2.
Make sure your application has the same DLL's as present in the
installation
Regards, Kenneth, GEOGRAF A/S
_______________________________________________
mapguide-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapguide-users
