Opened 12 years ago
Closed 12 years ago
#1933 closed task (invalid)
Revert back to TF.NET
| Reported by: | jng | Owned by: | jng |
|---|---|---|---|
| Priority: | low | Milestone: | Maestro-5.0 |
| Component: | Maestro | Version: | |
| Severity: | trivial | Keywords: | |
| Cc: | External ID: |
Description
The decision to move to .net Framework 4.0 has caused havoc for our NTS Thirdparty dependency.
Ideally we want a single ilmerge'd version of NTS that targets the .net Framework 4.0. Unfortunately, I have had lots of trouble getting the full NTS source and its dependencies to build. This is due to a key incompatibility between the GeoAPI and ProjNet sources and I have been unable to track down the key revision in ProjNet where this incompatibility was introduced.
At the end of the day, the main thing we want is a single library that exposes a simple geometry model for the Maestro API, with basic managed coordinate system functionality.
TF.net provided these qualities. Although it uses an old version of the respective libraries, the core functionalities worked, and at the end of the day, that is all we're really after.
So in the spirit of reducing NIH, Maestro should be using TF.net again, and we should contribute back any required modifications and fixes upstream as needed.
This constitutes another minor breaking change for consuming applications, which simply consists of namespace updates.
Long story short: This ticket undoes the changes of #1760
