Geek Answers Handbook

TFS 2010 Microsoft.Office.Interop Reference Woes

I'm going to go crazy with this problem!

  • I created a new server on a virtual machine for TFS.

  • I created a new assembly. The definition of what the solution registered on my local TFS machine is to build my solution using the default assembly process template.

  • On a TFS machine and my local I have MS Office 2010 and .Net framework 4.0.

  • In my project, I have a link to Microsoft.Office.Interop, etc.

  • All this works great on my local car.

The problem occurs when you run the assembly definition. The assembly starts and runs for a while until it reaches the links to the Microsoft assembly.

  • Type or namespace name 'Office'
    does not exist in the Microsoft namespace (do you miss the assembly?)

  • The type or namespace name "Application" was not found (are you missing the using directive or the assembly reference?)

  • Ect

Reference paths point to the GAC, if that matters.

Help would be awesome, and so you would be amazing at expanding.

Regards, Byron Cobb.

+4
source share
1 answer

Byron

If you take the builds from the compiled version on your computer, create the libs folder at the level of your solution, and then add the dll for

  • Microsoft.Office.Interop.Word.dll
  • Microsoft.Office.Interop.Excel.dll
  • Microsoft.Vbe.Interop.dll
  • office.dll

In the libs folder, then delete the link to your Office Interop and add links to the following assemblies in your libs folder, it should work with the processing we create without an office on our server assembly.

Hello

Yane

+10
source

More articles:


All Articles