Upgrading a VSTO Project to .net 4 - What Links Do I Really Need?

I am developing an application for Office. It was originally aimed at .net 3.5, but I decided to upgrade to .net 4 due to some WPF issues that I ran into.

When I switched all the projects in my solution and rebuilt, I received an error message including System.Xaml. I did this and rebuilt, and VS2010 told me to include another link, so I did. This happened a couple more times, and finally he asked to enable Microsoft.Office.Tools.Common.v9.0, and when I did this, I got this error:

Microsoft.Office.Tools.CustomTaskPaneCollection exists both in Microsoft.Office.Tools.Common.v9.0.dll and in Microsoft.Office.Tools.Common.dll

I have both Microsoft.Office.Tools.Common.v9.0 and Microsoft.Office.Tools.Common referenced in my project, but the problem is that if I delete, I get an error message. Am I doing something wrong? Is it strange that I need both links? It seems strange to me that CustomTaskPaneCollection will be defined in two different binaries.

If I delete Microsoft.Office.Tools.Common, then the error I get is "Cannot find the type of interaction that matches the built-in type of interaction" Microsoft.Office.Tools.IAddInExtension. "Do you have a link to the assembly?"

+3
source share
1 answer

'Microsoft.Office.Tools.IAddInExtension' Microsoft.Office.Tools.Common.dll. Microsoft.Office.Tools.Common.v9.0 . , - , , Microsoft.Office.Tools.Common.v9.0, Microsoft.Office.Tools.Common.dll. , . , / dll 4.0, DLL VSTO.

, .

+2

Source: https://habr.com/ru/post/1746000/


All Articles