How to Completely Remove Previous Versions of dotConnect Providers

How to Completely Remove Previous Versions of dotConnect Providers

Conflicts may occur if older dotConnect versions remain on the system, leading to installation errors or issues in Visual Studio. This article describes how to fully remove previous versions before reinstalling. The instructions apply to all dotConnect providers.

Common Error Messages:
  1. Installation error: Devart.Data assembly version … is found in Global Assembly Cache.
  2. Visual Studio error: The Devart.Data.… package did not load correctly.
Removal Procedure

Please reinstall dotConnect for (required provider) in the following way:

1.  Settings → Apps → Installed apps → Uninstall

Uninstall the following products:
  1. dotConnect … (all)
  2. Entity Developer
  3. LinqConnect
In most cases, this step is sufficient.

2. If the issue persists, confirm that no Devart.Data.* assemblies remain in the Global Assembly Cache:
  1. \Windows\assembly\GAC_MSIL\ (GAC 2.0)
  2. \Windows\Microsoft.NET\assembly\GAC_MSIL\ (GAC 4.0)
3. Remove any residual Devart-related directories if they exist:
  1. \Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\Extensions\Devart\
  2. \Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\Extensions\Devart\
  3. \Program Files (x86)\Devart\
  4. \Program Files (x86)\Common Files\Devart\
  5. \Program Files\Devart\
  6. \Program Files\Common Files\Devart\
  7. \ProgramData\Devart\dotConnect\
  8. \ProgramData\Devart\Entity Developer\
  9. \ProgramData\Devart\EntityDeveloper\
A file manager such as x-diesel Explorer may be used to verify that no leftover assemblies or folders remain.

4. Install dotConnect for (required provider) again.

Summary
Performing a full removal of previous versions and then reinstalling the required provider ensures a clean environment and prevents conflicts with outdated assemblies.

    • Related Articles

    • Installing Multiple Versions of dotConnect Providers on One Machine

      This article describes whether multiple versions of dotConnect providers can coexist on a single system. The information applies to all dotConnect providers. All dotConnect providers rely on a shared core assembly, Devart.Data.dll. Because this ...

    • Updating dotConnect to a New Version

      This article explains the procedure for updating dotConnect to the latest version. The instructions apply to all dotConnect providers. Update Procedure 1. Uninstall the previous version Open Settings → Apps → Installed apps → Uninstall and remove all ...

    • Where to Apply the License Key in dotConnect Providers

      License key usage in dotConnect providers varies depending on the target framework. In .NET Framework projects, licensing is managed automatically during installation, whereas .NET Core and later versions require the license key to be provided at ...

    • Installation vs. NuGet in dotConnect Providers

      dotConnect providers can be added to a project in two ways: by installing the product or by using NuGet packages. The choice depends on the project type and the .NET version you are targeting. This article applies to all dotConnect providers. Two ...

    • End-User Licensing and Deployment with dotConnect

      Applications developed with dotConnect can be distributed to end users without additional licensing costs. This article describes the licensing rules and deployment requirements. The information applies to all dotConnect providers. End users of an ...