Creating a new dataprovider

I'm fairly new to ADO.NET, I've written a couple client/server
applications that use the factory pattern in ADO.NET to work with MSSQL
and Oracle databases. Beyond that I'm fairly green.

My quest is to create a new community opensource project that consists
of an ADO.NET dataprovider to communicate with Windows Installer (
..MSI ) databases. Currently you have to P/Invoke to the MSI SDK API's
for opening databases, creating fiews, fecting records, accessing
records and so on and so on. I'd like to create a framework class that
I can share that is very ADO.NET friendly ( as much as applies to the
limitd abilities of an MSI database package ). My goal is to create
a framework for creating MSI applications/utilities/tools much easier
to design and develop.

Can anyone reccomend some good reading on how to go about this? I'm
guessing that there are a bunch of interfaces to derive from and
implement but I thought I'd ask for a point in the right direction
instead of spending alot of time in the sand traps.

Thanks,
Chris

.

Relevant Pages

  • Re: Business objects, subset of collection
    ... Non-CRUD/USER applications are not the sort of thing one tucks into eMails.] ... SQL databases sucks for searching large data sets, ... In CRUD/USER processing that is largely irrelevant because data is accessed once by each solution and seek time dominates the access performance issues in those situations. ... Lets say you want to find all unpaid invoices. ...
    (comp.object)
  • Re: Business objects, subset of collection
    ... might get faster applications than you would if you had used a SQL ... That is why databases using caching. ... there mainstream SQL databases wouldn't perform ... Lets say you want to find all unpaid invoices. ...
    (comp.object)
  • Re: 64-bit Thermal grease
    ... I can see it for databases, servers, etc., but what is there for the ... Just try to forget all the hype. ... So if you want an Oracle database then you are likely to find it in 64-bits, but for typical applications, there is no need. ... there are no Intel CPUs which have this 64-bit bias. ...
    (alt.comp.hardware.pc-homebuilt)
  • Re: whats the future of Object Oriented Programming
    ... big problems into smaller applications that feed off of databases. ... languages and functional languages, for example, offer still other ... Tool building, such as OS's, RDBMS engines, compilers, device drivers, ...
    (comp.object)
  • Re: Application logic and Business logic
    ... DBMSs are not for that. ... Any set of applications intended to manage databases is a DBMS. ... Good DBMS's are self programming systems. ...
    (comp.object)