MyDirect.NET 2.0 MySqlDataSource
Posted: Thu 29 Nov 2007 19:46
My goal is to port a working Web Site from MS SQL, ASP.NET 2.0 to MySQL. I've had many problems. The latest is:
DataBinding: 'System.Data.DataRowView' does not contain a property
with the name 'albumid'.
Note: albumid is in the DB table and the SELECT command works when executed in SQLyog.
I was hoping that switching from SqlDataSource (and FormView) to MySqlDataSource from MyDirect.NET would solve my problem, or make it easier to diagnose my problem. However, the problem remains.
The first two things I need from Core Lab is:
1) MySqlDataSource documentation. (Every other class is documented fully, but this one!)
2) C# DataSource Sample: When attempting to bring up Default.aspx in the MS VS Web Development Professional, it goes to the root of the Web project instead. I have tinkered with <authentication, <authorization, .. etc. in Web.config, but the beharior does not change. Do you have a Web.config code snippet that works?
This should enable me to gain confidence in 1) MySqlDataSource and 2) duplicate the problem in a small test case instead of a large one.
Thanks,
Kent
DataBinding: 'System.Data.DataRowView' does not contain a property
with the name 'albumid'.
Note: albumid is in the DB table and the SELECT command works when executed in SQLyog.
I was hoping that switching from SqlDataSource (and FormView) to MySqlDataSource from MyDirect.NET would solve my problem, or make it easier to diagnose my problem. However, the problem remains.
The first two things I need from Core Lab is:
1) MySqlDataSource documentation. (Every other class is documented fully, but this one!)
2) C# DataSource Sample: When attempting to bring up Default.aspx in the MS VS Web Development Professional, it goes to the root of the Web project instead. I have tinkered with <authentication, <authorization, .. etc. in Web.config, but the beharior does not change. Do you have a Web.config code snippet that works?
This should enable me to gain confidence in 1) MySqlDataSource and 2) duplicate the problem in a small test case instead of a large one.
Thanks,
Kent