Changes between Version 9 and Version 10 of GdalOgrCsharpVersions


Ignore:
Timestamp:
Apr 8, 2007, 4:36:21 PM (17 years ago)
Author:
tamas
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GdalOgrCsharpVersions

    v9 v10  
    22= GDAL/OGR CSharp interface versions =
    33
    4 The GDAL/OGR CSharp interface is fairly new and the first official version was published 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 the transition to the current development version is suggested for the interface users and 1.4.0 is considered as deprecated.
     4The GDAL/OGR CSharp interface is fairly new and the first official version was published 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 the transition to the current development version is suggested for the interface users and 1.4.0 will be considered as deprecated soon.
    55
    66== The main differences between 1.4.0 and 1.5.0, and the migration steps for the existing code ==
    … …  
    1010=== Support for the enumerated types of the C# interface (#1559) ===
    1111
    12 The 1.4.0 version treats the enumerated types as integers. Handling integers instead of enums is quite uncomfortable for the .NET developers since they don't enjoy the benefit of the autocompletion support of the IDE and it's quite an unconfortable to find out the possible values of a particular type. The 1.5.0 version exposes the enumerated types to the interface and therefore the programmer should use the proper values instead of using integer constants of the module class or using the constants from the gdalconst assembly. Every CSharp sample application has also been modified to reflect this behaviour.
     12The 1.4.0 version treats the enumerated types as integers. Handling integers instead of enums is quite uncomfortable for the .NET developers since they don't enjoy the benefit of the autocompletion support of the IDE and it's quite an uncomfortable to find out the possible values of a particular type. The 1.5.0 version exposes the enumerated types to the interface and therefore the programmer should use the proper values instead of using integer constants of the module class or using the constants from the gdalconst assembly. Every CSharp sample application has also been modified to reflect this behaviour.
    1313
    14 As an example in GDALColorTable.cs we use
     14As an example in GDALColorTable.cs we use:
    1515
    1616{{{