Error Setting Datasource in VS Community 2015 C # + ReportViwer + Mysql

2

Good afternoon. having a tremendous difficulty to solve this problem. I am in the distribution phase of an App and exactly today I had a serious problem.

Generate a report using RiportViwer and Mysql in VSC 2015.

Application running smoothly, however when creating a Datasource for use by Dataset, an error occurs.

Filed under: "mysql.data.MySqlClient '."

I do not know what to do, I already uninstalled the connector 6.9.9, I disabled the VS reportViewer and enabled it again, I got to install the odbc driver (which I do not particularly want to use).

If someone has ever had a similar problem, please feel free to help me.

    
asked by anonymous 31.03.2017 / 22:27

2 answers

1

James S, thank you very much for the feedback.

I would like to make a complement to the post of James (who solved in parts the problem that was happening).

I was able to see the following. When working with Mysql and VSCommunity (2015 have not tested on other versions), the developer or analyst should keep in mind that the versions of Mysql should be very well analyzed in the context of architecture.

When using mysql-for-visualstudio-2.0.4 or greater, you should use the Connector / Net 6.9.9. Versions prior to mysql-for-visualstudio-2.0.4 must use the Connector / Net version 6.9.8. (this was my problem.I'm using version 1.2.6)

In this way for any version of mysql-for-visualstudio, your connectr must be thoroughly analyzed.

Thanks for the opportunity.

Sds.

    
02.04.2017 / 20:53
0

Try this solution

  • Close Visual Studio
  • Removes MySQL Connector / Net installation
  • Install MySQL Connector / Net as you did before deleting (typical / custom).
  • Open Visual studio
  • Deletes all connections to the server / database / dataset from the solution and from the server explorer. (IMPORTANT: Do not remove any lines of code.)
  • Restore the connection to your database, naming it as it was.
  • Reestablish the connection to your data source for dataset as it was.
  • 31.03.2017 / 23:14