Data Source Configuration Wizard?
Posted: Tue 31 Jan 2006 20:04
I'm trying the MySQLDirect.NET provider to replace the MySQL Connector/.NET product, as I was impressed with the integration offered over the MySQL AB product. I'm working in VB, by the way.
One question though - I can't seem to get any integration with the VS2005 Data Source Configuration Wizard (DSCW), and if I try to add data sources, I can't select the MySQLDirect provider, only the MS ones supplied with VS2005.
Is there any integration at this level, or am I limited to dragging and dropping connections, commands and adapters onto a form, then generating a dataset?
On a related note, when generating datasets, is there any way to re-generate a dataset over the existing one, or do I have to delete and re-generate? Doing this means unhooking the dataset in many locations if I have used a common dataset in multiple forms. Of course, support for the DSCW would mean I could have common datasets in my application and use them in multiple forms and modules, which would be handy.
Last question: Is there any way to stop it asking me if i want to regenerate parameters? With a lot of datasets and lots of tables (my DB now has over 60 tables and growing!), this gets kind of tiresome...
Other than those small issues, great looking product so far, and I'm just trying to get enough of my app ported to MySQLDirect & framework 2.0 to prove that it all will work as I hope, then I'll be making a permanant jump and saying goodbye to the MySQL Connector/.NET.
Thanks & regards,
Chris
One question though - I can't seem to get any integration with the VS2005 Data Source Configuration Wizard (DSCW), and if I try to add data sources, I can't select the MySQLDirect provider, only the MS ones supplied with VS2005.
Is there any integration at this level, or am I limited to dragging and dropping connections, commands and adapters onto a form, then generating a dataset?
On a related note, when generating datasets, is there any way to re-generate a dataset over the existing one, or do I have to delete and re-generate? Doing this means unhooking the dataset in many locations if I have used a common dataset in multiple forms. Of course, support for the DSCW would mean I could have common datasets in my application and use them in multiple forms and modules, which would be handy.
Last question: Is there any way to stop it asking me if i want to regenerate parameters? With a lot of datasets and lots of tables (my DB now has over 60 tables and growing!), this gets kind of tiresome...
Other than those small issues, great looking product so far, and I'm just trying to get enough of my app ported to MySQLDirect & framework 2.0 to prove that it all will work as I hope, then I'll be making a permanant jump and saying goodbye to the MySQL Connector/.NET.
Thanks & regards,
Chris