Microsoft at its best.
Why have they left out the most flexible provider: OleDb ?!
I am sure the Entrerprise Library DAAB can be extended to support OleDb, but
they should have provided the support for it from the get-go.
I am sure it is a great academic exercise to complete the DAAB but how much
time and costs am I really going to save introducing these entreprise library
blocks in my development if I have to extend them before using them ? I mean,
this is not some dark custom provider, it is OleDb!
Makes me wonder if this is a pattern I can expect from the rest of the
Enterprise Library Blocks.
"Dmitriy Lapshin [C# / .NET MVP]" wrote:
> Hi,
>
> I am pretty sure you can extend it to support OleDB by implementing several
> provider-specific classes (and making changes to the provider factory in
> order to recognize the new provider type).
>
> --
> Sincerely,
> Dmitriy Lapshin [C# / .NET MVP]
> Bring the power of unit testing to the VS .NET IDE today!
> http://www.x-unity.net/teststudio.aspx
>
> "peterlip" <(E-Mail Removed)> wrote in message
> news:78828DA9-C522-4263-BA90-(E-Mail Removed)...
> > The Enterprise Library seems to have a lot of good stuff in it. However,
> > am
> > I missiing something, or is the Data Access Application Block JUST for
> > Oracle, SQL server & DB2. What about OLEDB for Access DBs????
>
>