Then I deleted the registry key value for (ONLY THE VALUE, NOT THE KEY ITSELF) Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Assemblies\GlobalĭocumentFormat.OpenXml,version=".0",culture="neutral",publicKeyToken="31BF3856AD364E35".Īnd that worked for me. I tried to uninstall it using GACUTIL.exe, but I got the above Message: Unable to uninstall: assembly is required by one or more applications Somehow the dll remains in the GAC and in the Registry. So I decided to uninstall the old SDK first by using the "Programs and Features" page and afterwards the "Uninstall"-Option of the MSI installer file. Press (F5) or click on Green Run Icon on ToolBar.Had the exact same problem with the OpenXml SDK Productivity Tool which only exists in version 2.5 but not in the latest 2.8.1.Īfter updating the SDK for my ASP.Net webpage in Visual Studio using Nuget Package Manager I had the problem that during the publish process the old "DocumentFormat.OpenXml V.2.5" dll was published and not the new one (which was referenced correctly in my Visual Studio project). Right-click each assembly file that is included in your application, click Uninstall, and then click Yes to confirm If you are unable to uninstall the dlls via the above method you can access the GAC folder without the special view by opening a run command and entering the path below and hitting enter. Replace the C:\PathOnServer\DLL.dll with the actual path of the DLL. Open the Windows PowerShell ISE from the Administrative tools on the server. It stores the assembly in a different GAC, the one in c:assembly. But I searched that WiX and MSI has the correct way of GACing the dlls, instead of using. $publish.GacInstall( "C:\PathOnServer\DLL.dll") I could use a custom action to gacutil the. ::Load( "System.EnterpriseServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a") In such scenarios the below PowerShell script does the job to install / uninstall DLLs from GAC. Most of the server environments lack the gacutil.exe as it is part of Visual Studio installation.
0 kommentar(er)
