Changes between Initial Version and Version 1 of Ticket #1760


Ignore:
Timestamp:
Jul 27, 2011, 5:10:46 AM (13 years ago)
Author:
jng
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1760

    • Property Summary Remove dependency on TF.net → Replace TF.net with NTS

  • Ticket #1760 – Description

    initial v1  
    99It will be simpler from a maintenance perspective to use NTS directly and provide our own MapGuide Geometry <-> custom geometry conversion. This opens up future lines of integration with NTS in the future, as we can keep NTS up to date as needed. Whereas tf.net is constrained by having seriously old version of NTS.
    1010
    11 To avoid leaking out the NTS dependency as Maestro currently does, it should define as much of the GeoAPI geometry interfaces directly in the Maestro API. The implementation specific Maestro API assemblies can then handle the required conversion logic as necessary. By not leaking out NTS dependencies, consuming applications will only need to reference the MaestroAPI assembly at compile time and not MaestroAPI + tf.net as it currently does.
     11~~To avoid leaking out the NTS dependency as Maestro currently does, it should define as much of the GeoAPI geometry interfaces directly in the Maestro API. The implementation specific Maestro API assemblies can then handle the required conversion logic as necessary. By not leaking out NTS dependencies, consuming applications will only need to reference the MaestroAPI assembly at compile time and not MaestroAPI + tf.net as it currently does.~~
     12
     13This represents a breaking API change. Applications using the MaestroAPI will now have to reference the merged NTS assembly instead of Topology.dll and will need to update namespace references