Installing Office Customization

Question

Name: From: file:///D:/Samples/TestUpdatedVersion/bin/Debug/TestUpdatedVersion.vsto

The customization cannot be installed because another version is currently insta

Answer 1

You can try to delete a registry key located at:

HKEY_CURRENT_USER\Software\Microsoft\VSTA\Solutions\{GUID}

The value of {GUID} will be different on your environment.

Check to ensure that you're deleting the right key. Confirm by checking the DWORD "Url" value at the key.

Restart Excel and you should be good to go.

Answer 2

Try uninstalling the previously installed VSTO application OR from the visual studio menu > Build | Clean Solution.

Answer 3

I was testing deployment after making the addin setup and facing the same problem when trying to install.

Issue: When you do a publish or debug the addin, VS would create/update the registry with this addin info under

HKEY_CURRENT_USER\Software\Microsoft\Office\Excel\Addins\<you addin name>\Manifest

this has the reference to the VSTO file that would be compared for doing upgrade. In your case, after you do publish, it would be pointing to

file:///D:/Samples/TestUpdatedVersion/bin/Debug/TestUpdatedVersion.vsto

Change this to your published vsto path. Now try to install, should work fine. You can test your auto upgrade options the same way, i.e. make a build+publish and change this path, then close all excels and open one.

Answer 4

try this link , you have a command to run in this page,just run it the problem will be fixed. command:

rundll32 dfshim CleanOnlineAppCache

See this link: How do I completely uninstall a ClickOnce application from my computer?

Answer 5

On development machine, on which I had built the VSTO Project in Visual Studio with the same Product Version / identity, I needed to execute Clean command by selecting the Project in Solution Explorer. In fact, this helped clear the registry entry, referred to above.

That allowed me to re-install the product with same application identity

Answer 6

What helped me in this issue was uninstalling the plugin from Control-M which I installed from my Published folder. And Clean the solution.