With the .NET MySQL Connector, I'm use VS2010. My old project at work began to report:
Error 175: The specified data store provider cannot be found, or is not valid.
I'm not sure why, but when MS suggested a patch for VS, things started acting strangely.
It turns out that when I choose to "Generate from database" while adding a test ADO.NET Entity Data Model to the project, the Entity Data Model Wizard does not display the data provider. Even worse, VS2010 enters a death spiral of dialog boxes when you right-click on an existing.edmx file and try to do a "Update Model from Database...," which can only be stopped using Task Manager.
Shut off VS2010 at This is how I resolve it.. Completely uninstall the MySQL Connector. Reboot. Completely install the MySQL Connector. Reboot. Relaunch VS 2010.
My data provider appears out of nowhere. My code can be compiled. Additionally, include test.edmx files. The wizard detects my MySQL database, approves the test connection, then uses my relational tables to create object models. I have complete freedom to clean and rebuild.
Before I start the software, everything is OK. My "repair" is ineffective.
The connection object is returning null at that moment, and if I recompile without making any code modifications, I receive the Issue 175 error once again. Rinse, repeat, and lather.
Using the MySqlConnection object, some experimenting with this StackOverflow response demonstrate that Connection String is legitimate are in this condition.
The issue seems to be that the data store provider is being stepped on or lost in some way, which affects EntityFrameworks' functionality.
I need some guidance on where to seek for these items to be kept, if anybody has come across something similar, and if there are any practical tips or recommendations you think I should attempt.
64 zzz zzzz Although this fact did not resolve my issue,
It did increase VS2010's stability. As soon as I removed the.NET Connector, I examined the list of installed applications in Control Panel and discovered there was still a previous version of the.NET Connector there. I removed the old one from the control panel, restarted the computer, and then installed the new one. The database provider for using EntityFrameworks is now stored in VS2010.. Evidently, when I installed a newer version of the MySQL Connector, I thought it would remove the older version; instead, they trample all over one other.
I'm receiving a
expressing the rather distinct meaning
The specified store provider cannot be found in the configuration, or is not valid. System.ArgumentException: Unable to find the requested .Net Framework Data Provider. It may not be installed.
This takes place at the
1002 zzz — The above strikeouts were necessary since VS2010 finally lost the settings once again. But without having to reboot, I was able to remove the.Net Connector from the control panel and install it again, restoring my data provider to the environment. This aspect of the issue seems to be more of a VS2010 flaw than a.NET Connector problem.
After considerable upgrades, the issue disappeared, suggesting that it was perhaps a driver or environment flaw.