SQL Source Control Error - Error on linking db. Could not load file or assembly Microsoft.TeamFoundation.Core.WebApi

[vansadersk]

I am currently evaluating SQL Developer Bundle particularly for the purpose of Source Control + DevOps Automation. Upon first attempt to link a database to a git repository I get this error and cannot move forward. I just downloaded and installed the bundle today, so it should be the latest version. When I check the version however, it says 1.5.52 for Source Control

Severity Code Description Project File Line
Error Could not load file or assembly 'Microsoft.TeamFoundation.Core.WebApi, Version=3D15.0.0.0, Culture=3Dneutral, PublicKeyToken=3Db03f5f= 7f11d50a3a' or one of its dependencies. The system cannot find the file specified. Source Control: dbtest(192.168.2.16) 1

[alexa]

You are using an obsolete product version. Please upgrade it to the latest version 2.0 https://www.devart.com/dbforge/sql/sour ... nload.html

[vansadersk]

This is exactly where I downloaded the bundle from, only yesterday. Is the Source Control version in the bundle wrong? How can I get a standalone download of the correct version?

[vansadersk]

@alexa,
Here is the screenshot when I open the linked installer:

[alexa]

Thank you for bringing this to our attention.

We will fix this issue with the old version on the website shortly.

[vansadersk]

@alexa,
Was the team able to produce an updated install package? If my company is going to seriously consider devart's products, this needs to work. Is there a standalone installer of the 2.x version available at least?

[vansadersk]

The new version works, thank you.

[alexa]

Thank you for letting us know this.

[clavacca]

Same problem here.

I'm using dbForge Studio (paying customer), have been using it for years.

Suddenly, Source Control stopped working, showing this error message.

I have already installed the latest version. I tried setup Repair option to re-generate assemblies. No luck.

I am using Visual Studio Pro 2019 (latest version), with all updates installed.

Please advise.

[clavacca]

Unfortunately, the only solution I found was to uninstall dbForge Studio and roll back to an OLDER version.

This is definitely a bug on dbForge Studio for SQL Server v.5.7.99 (Jul 9, 2019)

dbForge Studio for SQL Server v.5.6.104 (Dec 22, 2018) works fine.

[alexa]

The fix is not yet included in dbForge Studio for SQL Server. It's only fixed now in dbForge Source Control for SQL Server, v2.0 https://www.devart.com/dbforge/sql/sour ... nload.html