[mapguide-internals] RE: Refactoring Web .NET API into Common DLLs is ready for review.

Leaf Li leaf.li at autodesk.com
Thu Jun 25 10:03:35 EDT 2009

The key motivation of this RFC is to let other application be able to resue MapGuide's code.
1. It is ture .NET developer need update their project to add new reference after this RFC is implemented. However, they may still need rebuild their project without this RFC after using a new version of MapGuide because of some changes to .NET API. So adding some new references to their project is really a minor changes.
2. Currently MapGuide .NET Web API depends on MapGuide environment. It is nearly for other application to reuse MapGuide .NET API. After refactoring MapGuide .NET Web API into some common dlls, APIs in Foundation, Geometry and PlatformBase components can be completely used by other applicaiton such as coordinate system API. In that time, MapGuide is not only a Web GIS platform. but also a GIS platform which can be used by both desktop applicaiton and web applicaiton.

Leaf Li

From: Leaf Li
Sent: Thursday, June 25, 2009 6:47 PM
To: mapguide-internals at lists.osgeo.org
Subject: RE: Refactoring Web .NET API into Common DLLs is ready for review.

I think Jason just gave us a very good sample of one of the benefits to this RFC. Users can develop other application based on MapGuide API. Actually those application can be both desktop and web application. I am not sure whether we can have a MapGuide .NET Desktop SDK currenlty. It isn't difficult for users to copy several files manually before we have it as long as we document it.

Leaf Li

More information about the mapguide-internals mailing list