[mapguide-internals] MapGuide RFC 68 - Refactoring Web .NET API
into Common DLLs is ready for review.
jumpinjackie at gmail.com
Wed Jun 24 02:43:47 EDT 2009
Is the current MapGuideDotNetApi.dll that "heavy" that it needs to be split
up into multiple sub-assemblies?
And also, just a personal thing really, I never really knew which MG API
classes were Foundation, which were PlatformBase, etc since they all resided
under the OSGeo.MapGuide namespace. Having these classes split up but still
under the same namespace will no doubt cause some (short term) confusion.
So is my first point enough justification for the move?
Leaf Li wrote:
> Please review MapGuide RFC 68 - Refactoring Web .NET API into Common DLLs
> Post any comments or questions to the mailing list.
> Leaf Li
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
View this message in context: http://n2.nabble.com/MapGuide-RFC-68---Refactoring-Web-.NET-API-into-Common-DLLs-is-ready-for-review.-tp3146189p3147075.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.
More information about the mapguide-internals