C
Christopher Painter
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
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