To maintain similarity and familiarity across .NET Framework data providers, use the following code conventions.
Naming Conventions
To maintain consistency across .NET Framework data providers, preface the classes implemented in your .NET Framework data provider with an identifier that is unique for your implementation. For example, a sample .NET Framework data provider might use "Sample" as a unique identifier and implement IDbConnection as "SampleConnection", IDbCommand as "SampleCommand", IDataAdapter as "SampleDataAdapter", and so on.
Constructors
Although not a required part of the implementation of the ADO.NET interfaces, there is a standard set of constructors that should be implemented in each .NET Framework data provider to help ensure a consistent programming model. The following table lists the constructors that should be implemented in every .NET Framework data provider. In the constructor names listed, Prv is a placeholder for the unique identifier for your class name.