I experienced a fatal error when I tried to export data from a Mysql database in Visual Studio. The database is on an Azure VM.
The error occurred after I selected a database(censored database name on the combobox). At first, the combobox was empty. I selected A database then Visual Studio Crashed. I repeated the procedure and it all results into Visual Studio 2013 crashing.
I reopened Visual Studio and tried looking for any clues regarding the crash. I easily found a related error.
The error appears after clicking the item highlighted above. Interacting with the prompt is harmless.
The prompt indicated that there is a problem in getting the information regarding the database. The Access issue might have also occurred in the fatal error. Nevertheless, Visual Studio should have not crashed due to a disconnection. There should have been a fail safe or an error handler for this kind of situations. An error prompt like the one that appeared on the non fatal issue would have been nice instead of crashing Visual Studio.
The experience highlights that connecting on an external Mysql database from an Azure VM can be troubling. I also experienced server disconnection as seen in server explorer. Question is how to make databases connections to Azure VMs be reliable
