Resolving Assembly Version Issues by Cleaning the Global Assembly Cache (GAC)
You might encounter assembly version conflicts if an incomplete uninstall of a previous dotConnect provider leaves an empty folder in the Global Assembly Cache (GAC). This is an uncommon occurrence.
Accessing the Global Assembly Cache:
The Global Assembly Cache (GAC) is typically located at:
C:\Windows\assembly\GAC_MSIL\

Note: you cannot directly access this folder using standard Windows Explorer due to its special shell extension.
Solution 1: Using a File Manager with System Administrator Permissions
For easier access, use a file manager (such as Unreal Commander) that allows viewing hidden and system files. Run the file manager with system administrator privileges. Navigate to the C:\Windows\assembly\GAC_MSIL\ folder and delete the Devart.Data folder.
Solution 2: Disabling the GAC Shell Extension in Explorer
If you only have Windows Explorer, you can disable the GAC shell extension to access the folder's contents. The shell extension is enabled through the Desktop.ini file within the assembly folder. Follow these steps in Command Prompt:
1. Navigate to the GAC folder:
cd %windir%\assembly
2. Remove system and hidden attributes from the Desktop.ini file:
attrib –s –h desktop.ini
3. Rename the Desktop.ini file to disable the shell extension:
ren Desktop.ini Desktop.ini.disabled
After executing these commands, you can use Windows Explorer to navigate to the %windir%\assembly\GAC_MSIL\ folder and delete the Devart.Data folder.
Finally, to re-enable the GAC shell extension, rename the Desktop.ini.disabled file back to Desktop.ini in the Command Prompt:
ren Desktop.ini.disabled Desktop.ini
Related Articles
Assembly version is found in Global Assembly Cache
The issue can occur if gacutil left an empty folder in the \GAC_MSIL\ after uninstalling a previous version of a dotConnect provider. This is a very rare case in fact. The Global Assembly Cache can be found here: ...
Troubleshooting Debugger Configuration Issues
When using SQL Complete, the integrated debugger must be configured correctly to function as intended. If you're encountering issues with debugger initialization or behavior, this guide provides key troubleshooting steps and reference resources to ...
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 ...
Troubleshooting Devart Account or File Download Issues
If you’re experiencing problems with accessing your Devart account, pages not loading correctly, or being unable to download files, please follow the steps below to troubleshoot the issue and help our support team assist you efficiently. Before ...
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 ...