none
Publish generates "Error 2 An error occurred generating a bootstrapper"; workarounds fail. RRS feed

  • Question

  • I am a new Visual Studio 2010 user attempting to create a Word 2010 add-in.

    The project debugs without error, but publish creates this error: "Error 2 An error occurred generating a bootstrapper: Unable to begin updating resource for bin\Debug\app.publish\setup.exe with error 80070002 ProofOfConceptAddIn". I am running Windows 7 (64-bit) with Intel I7 CPU.

    I've seen the following workarounds recommended:

    Change the "Platform Target" from x86 to "Any CPU"
    "Any CPU" is already set.

    Downgrade solution to VS2008
    Haven't tried because I don't know how.

    Inside bin folder, delete Debug folder and Release folder.
    Seems like voodoo but I deleted Debug. Release wasn't present. No change.

    More voodoo: I tried publishing to another drive. No change.

    Am I waving the chicken clockwise when I should be waving it counterclockwise? Given the fact that I have little experience with VB and have had Visual Studio installed for less than a week, it's entirely possible that I'm missing something that's absurdly obvious.

    Clues appreciated!

    Tuesday, June 28, 2011 12:18 PM

Answers

  • I have, with help, found a workaround.

    Thanks to a clue from Bill Sempf, co-author of VSTO for Dummies, I tried running Visual Studio 2010 "As Administrator". Publish succeeded.

     

    Wednesday, June 29, 2011 10:27 AM

All replies

  • I have, with help, found a workaround.

    Thanks to a clue from Bill Sempf, co-author of VSTO for Dummies, I tried running Visual Studio 2010 "As Administrator". Publish succeeded.

     

    Wednesday, June 29, 2011 10:27 AM
  • I tried the workaround of running "As Administrator". It worked. I was so relieved. However, when I modified the project and then tried to pubish again I was back to "Error 2 An error occurred generating a bootstrapper"


    However, a workaround that works for me (although it means temporarily disconnecting from the network) is by disabling my antivirus. I don't think this is the best solution and will endeavour to find an acceptable alternative.
    • Proposed as answer by SylphLikeSi Friday, July 15, 2011 1:40 PM
    • Unproposed as answer by SylphLikeSi Friday, July 15, 2011 1:41 PM
    • Proposed as answer by SylphLikeSi Friday, July 15, 2011 1:44 PM
    Friday, July 15, 2011 9:54 AM
  • Did you choose Run As Administrator the second time you published the application? I have compiled several solutions many times and have not experienced another instance of the failure as long as I select Run As Administrator each time. That's the only difference that occurs to me.
    • Edited by OrangeCatGuy Friday, July 15, 2011 9:18 PM Previous message was unclear.
    Friday, July 15, 2011 8:59 PM