Those dlls in question are not .net assemblies. I don't know why VS would try to process them for metadata. Maybe because they're dlls in your output directory. Either way it should not be an issue.
Local IIS debugging means that IIS will probably still have open handles on your dlls from a previous VS debugging run hence the "sharing violation" message. You'll have to recycle the associated application pool in IIS to free these handles. Ugly solution, but there doesn't seem to be a better way. - Jackie -- View this message in context: http://osgeo-org.1560.x6.nabble.com/64-bit-woes-tp4182647p5050110.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
