none
Just starting add-in devel - unable to Debug VS 2010, Office 2007 Word App Add-in RRS feed

  • Question


  • Paul Foster

    I've spent about 4 hours searching the forums, trying suggestions, and just not getting anywhere. Steps I followed:

    1. Created a new Word 2007 App Add-in project in VS 2010.

    2. F5. Result:

    Could not load file or assembly 'WordAddIn1, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. Access is denied.


    3. Signed the Assembly using the "WordAddIn1_TemporaryKey.pfx" default provided key.

    4. F5. Result:

    Could not load file or assembly 'WordAddIn1, Version=1.0.0.0, Culture=neutral, PublicKeyToken=016fb6ef960fe09b' or one of its dependencies. Access is denied.




    I verified that .Net Programability support is enabled for Word (and other office apps)



    Looking at the References that were auto-added to the project:

    - Microsoft.Office.Interop.Word: 12.0.0.0

    - Microsoft.Office.Tools: 10.0.0.0

    - Microsoft.Office.Tools.Word: 10.0.0.0



    From the Project Properties:

    - Target framework: .NET Framework 4 Client Profile

    - Conditional compilation symbols: VSTO40

    - Sign the ClickOnce manifests: (auto created when I ran) Issued to me, expires in a year

    - Sign the assembly - as noted above, using default key file.





    Checking Microsoft Word 2007 --> Word Options --> Add-Ins --> COM Add-Ins:

    - Visual Studio Tools for Office Design-Time Adapter for Word is an Active Application Add-in (also shows enabled under COM Add-ins)

    - I do have a number of other Word Add-ins installed such as DOORS (from Telelogic), Acrobat, Nuance PDF, and they all function normally within Word.

    • Edited by pfoster Saturday, March 17, 2012 9:38 AM IE wouldn't actually submit forum content - security error on page. Submitting via firefox.
    Saturday, March 17, 2012 9:33 AM

Answers

  • do you have any anty-vir software running? try disabling it .
    • Marked as answer by pfoster Sunday, March 18, 2012 10:49 PM
    • Unmarked as answer by pfoster Sunday, March 18, 2012 10:49 PM
    • Marked as answer by pfoster Wednesday, March 21, 2012 8:06 PM
    Saturday, March 17, 2012 9:50 PM

All replies

  • do you have any anty-vir software running? try disabling it .
    • Marked as answer by pfoster Sunday, March 18, 2012 10:49 PM
    • Unmarked as answer by pfoster Sunday, March 18, 2012 10:49 PM
    • Marked as answer by pfoster Wednesday, March 21, 2012 8:06 PM
    Saturday, March 17, 2012 9:50 PM
  • I believe you're right. From my McAfee VirusScan Enterprise Access log:

    3/18/2012    6:45:05 PM    Blocked by Access Protection rule     A****\p****r    C:\Program Files (x86)\Microsoft Office\Office12\WINWORD.EXE    C:\USERS\*****\APPDATA\LOCAL\ASSEMBLY\TMP\PL9AXL5P\WORDADDIN1.DLL    User-defined Rules:Prevent Word from Creating or Modifying DLLs    Action blocked : Create

    The problem is, IT password protects the user interface to McAfee, so I can't disable the on access scan without their help. Will mark this as the answer when I have gotten help from them and prove that was the issue.


    Paul Foster

    Sunday, March 18, 2012 10:52 PM
  • This article describes the problem. In short, VSTO uses shadow copy to update DLLs that are in use. According to my IT org, this remains a SERIOUS security risk. I'm going to use a shared add-in project type, which doesn't use shadow copy and live with the limitations.

    Paul Foster

    Wednesday, March 21, 2012 8:08 PM