| | 5 | The CSharp interface has been build upon a common ground as the other SWIG generated wrappes (like Perl, Python, Java, PHP and Ruby). In this regard the class names and class member names along with the method signatures are fairly predestinated and might not follow the conventional .NET naming guidelines. However, one can easily identify the counterpars of the members in the GDAL/OGR API documentation. |
| | 6 | The GDAL/OGR CSharp classes use the .NET ''P/Invoke'' mechanism for the communication between the managed and unmanaged code. Every class implements the ''IDisposable'' interface to control the finalization of the underlying unmanaged memory referenced by every the wrapper class. |
| | 7 | |
| | 8 | = Supported platforms = |
| | 9 | |
| | 10 | Currently the interface is compilable and supports the various Win32 and Win64 platforms targeting the Microsoft.NET and the MONO framework. The interface is also compilable under the GNU Linux/OSX systems for the MONO framework. The compilation steps for the various platforms have been added to the [http://buildbot.osgeo.org:8500 GDAL buildbot] and tested regularly. |
| | 11 | |
| | 12 | = CSharp interface versions = |
| | 13 | |
| | 14 | The GDAL/OGR CSharp interface is fairly new and the first official version was published first along with the GDAL 1.4.0 release. As of the 1.4.0 release there was a substantial evolution in the interface based on the various user requests. Some of these changes in the current version (1.5.0) were backward incompatible with 1.4.0 and currently the transition to the current development version is suggested for the interface users and 1.4.0 is considered as deprecated. |
| | 15 | |
| | 16 | = The main differences between 1.4.0 and 1.5.0, migration steps for the existing code = |
| | 17 | |
| | 18 | TODO |
| | 19 | |
| | 20 | = GDAL/OGR CSharp interface compilation = |
| | 21 | |
| | 22 | TODO |
| | 23 | |
| | 24 | = Using the GDAL/OGR CSharp interface = |
| | 25 | |
| | 26 | TODO |
