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

[Kenneth Skovhede, GEOGRAF A/S]

There was (again) some changes to the inheritance of one or more classes,
with regards to the MgDisposable and MgGuardedDisposable,
so the current .Net dll will not work with updated native dll's.

The current natives will not work well with the new MG server.

However, it is possible (a bit cumbersome though) to bind to
the new version of the .Net assembly, using web.config or app.config,
and thus use the new dll without recompiling.

Splitting the dll would remove that option.

Regards, Kenneth Skovhede, GEOGRAF A/S



Andy Morsell skrev:
> Item 1 also has me very concerned.  There are a lot of existing .NET based
> MGOS / MGE applications out there.  Some are in direct control of the user
> so they may be able to update their .NET project, but many are delivered by
> consultants.  W the user updates to a newer release of MGOS / MGE it is not
> a good idea for their application to be broken and then have to go back to a
> consultant to fix it for them.  For these types of folks (not programmers),
> they won't know that their application will break until it's too late.
>
> Your statement of " they may still need rebuild their project without this
> RFC after using a new version of MapGuide because of some changes to .NET
> API" also has me concerned.  Can you please elaborate on this a little?
>
> Thank you.
>
> Andy 
>
>
> -----Original Message-----
> From: Leaf Li [mailto:leaf.li at autodesk.com] 
> Sent: Thursday, June 25, 2009 7:04 AM
> To: mapguide-internals at lists.osgeo.org
> Subject: [mapguide-internals] RE: Refactoring Web .NET API into Common DLLs
> is ready for review.
>
> 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.
>
> Thanks,
> 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.
>
> Thanks,
> Leaf Li
>
>
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>