Installing MySQL for Visual studio pits

Read Catalogue

• Problem description
• Resolution process
• Solution Solutions
• Summarize

Back to the top of the problem description

Installing MySQL for Visual Studio is generally intended to be able to select the MySQL type in the data source for the server data connection to VS, such as:

But sometimes, obviously installed successfully, but can not find the MySQL data source. In future situations you will encounter:

1. After installing VS, re-open the installation program to modify the installation location;

2. VS2013 and VS2015 are installed at the same time, and are installed separately in different locations (in which case there will be only one version of VS successfully installed);

3. Other situations that may exist .....

Back to top of the resolution process

The first doubt is that mysql-for-visualstudio-1.2.*.msi this package is not installed properly, then open the installation package, if the installation was successful (whether or not installed correctly), there should be a few options:

Repair was tested without any eggs, and the change was chosen.

If the installation is not successful, the initial installation interface will appear.

To solve the problem, you should naturally choose custom that sees all the installation options.

The Chang and custom options will jump to the custom installation screen.

By expanding the menu, you will find that the entity Framework support for VS is not selected, and it seems the problem is that this thing has not found the VS path because of inexplicable reasons, so no extensions are installed.

I try to hook it up manually, then install it next, and then open the VS discovery that still has no OVA. However, on my PC's largest disk root directory found vspath20**, such as I manually hook up 2015, then there will be VSPath2015, and the directory structure is as follows:

I can see that the goods are really not up to the VS installation path, and then we find a big open space to put this extension down.

See this, I think almost all can think of to copy this thing to the VS installation directory, so I did so, open vs, still no eggs.

Then I looked it up on the Internet and finally found the command for the VS reload extension.

. \devenv.exe/setup

This time again open, there will be a hint loading * * * *. When VS is officially open, you finally find this thing in the data source list.

Back to top solution

The following is a simplified solution based on the resolution process.

1. Re-open Mysql-for-visualstudio-1.2.*.msi, select Change or custom;

2. Expand the last menu and tick the VS version of the response;

3. After installation, find a folder such as vspath20** on the largest hard disk on the local free space, and copy over the VS installation path (see where the folder name should be covered);

4. Open the command line and navigate to the VS program devenv.exe path and execute the following command to reload the extension.

. \devenv.exe/setup

Back to top of the summary

Other aspects of extended load problem estimation can also be solved in this way, but not necessarily solve all the similar problems.

Installing MySQL for Visual studio pits