Entity Developer 6.x install sets no DB type mappings in Visual Studio 2015 - Resolved

[BChaney]

We're running into an odd installation problem with some of our Entity Developer Pro 6.x installs. The Visual Studio plugin shows no database type mappings for any database flavor in the the server options. This is causing issues when saving models. The server options & model behavior are both fine in the standalone tool.

This problem does not occur with the latest 5.8.x plugin nor does the 6.x problem occur in all cases. So far, I've been unable to determine what is making the difference between the installs that work & the ones that don't. All our Visual Studio installs are similar in configuration. Anyone seen this before or have any ideas on how to troubleshoot this?

[Shalex]

The server options & model behavior are both fine in the standalone tool.

This problem does not occur with the latest 5.8.x plugin nor does the 6.x problem occur in all cases. So far, I've been unable to determine what is making the difference between the installs that work & the ones that don't. All our Visual Studio installs are similar in configuration. Anyone seen this before or have any ideas on how to troubleshoot this?

Entity Developer stores server options in registry. If you run your Visual Studio with a lack of permissions, this can explain the behaviour you have encountered. Please install Entity Developer via As administrator menu options and run your Visual Studio via As administrator as well. Does this help?

The Visual Studio plugin shows no database type mappings for any database flavor in the the server options.

1. Please send us a screenshot of the issue.

This is causing issues when saving models.

2. Give us a detailed descriptions of the issues.

[BChaney]

Apologies for the delay. I didn't expect a quick response & was then out of the office.
Today, I tried version 6.0.96 on one of the misbehaving machines and the symptoms persist.
As requested, I sent a screenshot of the empty server options and of the assembly error dialogue we get when using the plugin.
The developers are local admins on their machines, which is how the installs got done.
Running Visual Studio as Administrator does not correct the symptoms.

[Shalex]

We have asked for the additional information by email.

[BChaney]

Replied via email with the additional information.

[BChaney]

Worked with Oleksandr in Support.
Looks like the culprit was product version 13.0.1601.5 of the Microsoft.SqlServer.Types assembly.
The easiest resolution for the remaining problematic machines will be to apply the latest SSDT update.
The plugin works appears to work properly with the newer version of the assembly.

Thanks for the help, Oleksandr!

[Shalex]

Thank you for letting us know.