[英]Issue with MySQL for Visual Studio / Visual Studio 2017 Datasource Wizard. Object reference not set to an instance of an object
Windows 10 Pro Windows 10专业版
Visual Studio 2017 Pro - 15.5.6 Visual Studio 2017专业版-15.5.6
MySQL for Visual Studio - 1.2.7 适用于Visual Studio的MySQL-1.2.7
MySQL Connector/NET - 6.10.6.0 MySQL连接器/ NET-6.10.6.0
I have encountered an issue with MySQL for Visual Studio. 我在MySQL for Visual Studio中遇到问题。
When opening the 'Configuring a Data Source' dialog box, and adding a query, I can query the data fine. 打开“配置数据源”对话框并添加查询时,我可以很好地查询数据。
When running the Test Query on the final screen, it fails with the following error: 在最终屏幕上运行测试查询时,它失败并显示以下错误:
When finishing the configuration without testing the query, and subsequently running the debug - an Object Reference exception is thrown as shown below: 在不测试查询的情况下完成配置并随后运行调试时,将引发对象引用异常,如下所示:
I have tested this on other solutions that previously worked, but I am getting the same issue. 我已经在以前可用的其他解决方案上进行了测试,但是遇到了同样的问题。
Any ideas guys? 有想法吗?
Fixed it. 修复。 For anyone who is interested - I did the following:
对于任何有兴趣的人-我做了以下工作:
There appears to be an issue with the latest version of Connector/NET. 最新版本的Connector / NET似乎有问题。
I have posted this as a MySQL Connector/NET Bug. 我已将其发布为MySQL Connector / NET Bug。
This also occurs in VS2015 using anything over MYSQL for VS 1.2.4 and Connector/NET 6.9.8. 这在VS2015中也会发生,在VS 1.2.4和Connector / NET 6.9.8上使用MYSQL上的任何内容。 When VS2017 was first released it worked with MYSQL but it breaks after making any changes to the MYSQL components, eg upgrading to the latest GA release.
VS2017首次发布时,可与MYSQL一起使用,但对MYSQL组件进行任何更改(例如升级到最新的GA版本)后,它便会中断。 I cannot remember the original configuration for the working VS2017.
我不记得正在运行的VS2017的原始配置。 I have tried all combinations of MYSQL for VS and connectors but nothing has worked.
我已经尝试过将MYSQL用于VS和连接器的所有组合,但是没有任何效果。 Eventually I went back to 2015 because 1.2.4 does not support 2017. (Tried on both Windows 10 Home and Professional) I suppose my answer is downgrade to VS2015, which is not really a fix.
最终我回到2015年,因为1.2.4不支持2017。(在Windows 10 Home和Professional上都尝试过)我想我的答案是降级到VS2015,这并不是一个真正的解决方案。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.