102 | | With the introduction of the class ''!FdoICapability'', all other capability classes – ''FdoICommand'', ''FdoIConnection'', ''FdoIExpression'', ''FdoIFilter'', ''FdoIGeometry'', ''FdoIRaster'', ''FdoISchema'', ''FdoITopology'' – including their interfaces become obsolete. There is no immediate plan to depricate those classes and functions but the intend is to do it eventually. Therefore, any application that uses the FDO capability interfaces should use the new interfaces once they become available to minimize later code changes. |
| 102 | With the introduction of the class ''FdoICapability'', all other capability classes – ''FdoICommand'', ''FdoIConnection'', ''FdoIExpression'', ''FdoIFilter'', ''FdoIGeometry'', ''FdoIRaster'', ''FdoISchema'', ''FdoITopology'' – including their interfaces become obsolete. With the exception of the class ''FdoITopology'', there is no immediate plan to depricate those classes and functions but the intend is to do it eventually. Therefore, any application that uses the FDO capability interfaces should use the new interfaces once they become available to minimize later code changes. |
| 103 | |
| 104 | As mentioned, the exception is the class ''FdoITopology''. The reason why this class will be depricated immediately is the fact that FDO does not support topology and therefore the presence of topology capability is inconsistent. The proposed change deletes the class ''FdoITopology'' and its counterpart in the managed code base as well as any reference to those classes in FDO code. |