http://docs.openlinksw.com/st/dotnet.html ADO.NET Data Providers OpenLink Lite Documentation 2008-10-12T02:09:59Z http://docs.openlinksw.com/st/../images/lite/misc/logo.jpg http://docs.openlinksw.com/st/dnetarch.htmlArchitecture 2008-10-12T02:09:59Z Architecture From the outset one of the main design goals of the .Net Data Provider was to implement a generic client layer enabling the re-use of our existing data access components for connecting to remote data sources. This has been achieved with both our Managed and Unmanaged .Net Data Providers, each of which have a common namespace that eliminates the need to recompile applications should the need arise to change the remote data source. http://docs.openlinksw.com/st/dnetdevel.htmlDeveloping .NET Data Provider Application 2008-10-12T02:09:59Z Developing .NET Data Provider Application The namespaces for the OpenLink .Net Data Providers are: A .NET data provider provides functionality for connecting to a data source, executing commands, and retrieving results. Those results can be processed directly, or placed in an ADO.NET DataSet for further processing while in a disconnected state. While in the DataSet, data can be exposed to the user, combined with other data from multiple sources, or passed remotely between tiers. Any processing performed on the data while in the DataSet can then be reconciled to the data source. All .NET data providers are designed to be lightweight. They consist of a minimal layer between the data source and your code. This extends functionality without sacrificing performance. http://docs.openlinksw.com/st/dnetconnstr.htmlOpenLink .NET Data Providers Connect String Attributes 2008-10-12T02:09:59Z OpenLink .NET Data Providers Connect String Attributes This section details the Connect string attributes an ADO.Net application can pass to the OpenLink .Net Data Providers when attempting a connection to a remote database. http://docs.openlinksw.com/st/dnetclasses.htmlOpenLink .NET Data Providers Class Implementation 2008-10-12T02:09:59Z OpenLink .NET Data Providers Class Implementation This section details the classes exposed by the OpenLink .NET Data Providers, which users must be familiar with in order to make effective use of the providers. Many of the OpenLink Generic Provider classes implement interfaces or inherit from the .NET Framework namespaces System.Data and System.Data.Common. A summary of the classes exposed by the provider is given below. The table only shows classes or interfaces inherited from System.Data or System.Data.Common. Some of the OpenLink.Data.GenericClient classes implement additional interfaces or inherit from a class belonging to a namespace other than System.Data or System.Data.Common. These details are not shown. For full details refer to the detailed documentation for the appropriate class in OpenLink.Data.GenericClient Namespace. http://docs.openlinksw.com/st/dnetnamespace.htmlOpenLink.Data Namespace 2008-10-12T02:09:59Z OpenLink.Data Namespace All the public classes in the OpenLink.Data namespace are detailed in this section. Note that all of the OpenLink .Net Data Providers use the same common class names, thus the descriptions below are applicable to all enabling maximum re-use of code across Providers. IMPORTANT: Public class members inherited from a base class defined by the .NET Framework Class Library (FCL), or which implement an FCL defined interface method, are not described. For details of these inherited members, refer to the .NET FCL documentation for the base class or interface. Where an OpenLink class implements an ADO.NET interface and adds additional methods or properties, these extensions are documented. In the class descriptions which follow, all code extracts showing partial class definitions, method signatures etc. are in C#. Examples for other .NET languages are not shown. http://docs.openlinksw.com/st/dnetissues.htmlKnown Issues 2008-10-12T02:09:59Z Known Issues http://docs.openlinksw.com/st/dnettest.html.Net Provider Test Program 2008-10-12T02:09:59Z .Net Provider Test Program A simple .Net interactive SQL program is provided for enabling a test connection to be made with the UDA Managed and/or Unmanaged .Net Data Providers, as indicated in the screen shots below: The connect strings for the Managed .Net Providers (GenericClient, MS SQLServer and Sybase) are similar with the 'Port' attribute designating the location of the Service to which is connection will band made. The Unmanaged OdbcClient provider differs as indicated below: http://docs.openlinksw.com/st/features_dotnet.xml.htmlNew Features 2008-10-12T02:09:59Z New Features