none
MS Project Addin - x64 RRS feed

Answers

  • no, your add-in code should be anycpu and your installer target platform should match your office bitness (x86 here). To avoid publisher not verified window on first start after installation you can either make your plugin compile against .net 4.0 and install it into %programfiles% or you can add custom action to installer to add entry to inclusion list for vsto
    Tuesday, May 29, 2012 9:46 AM

All replies

  • Hi Banng,

    Thanks for posting in the MSDN Forum.

    I would recommend you confirm two things:

    1. Whether Office is 64-bit?
    2. Whether platform is 64-bit?

    There are several combinations, different combination need different solution.

    Have a good day,

    Tom


    Tom Xu [MSFT]
    MSDN Community Support | Feedback to us

    Thursday, May 24, 2012 4:50 AM
    Moderator
  • Hi Tom_Xu MSFT,

    Thanks for the reply.

    1. I am using MSproject-2007 (sp2) 32-bit.

    2. Machine i m using is  Windows server 2008 - 64 bit.

    Could you please tell me how to go about this ?

    Thanks again!


    • Edited by Banng Thursday, May 24, 2012 5:56 AM
    Thursday, May 24, 2012 5:52 AM
  • Hi Tom_Xu,
    I am able to resolve the issue.
    Only problem currently I am facing is, I am getting pop up as
    “Publisher cannot be verified” are you sure, You want to install customization.
    This is while loading addin.
    How can I resolve this ?

    Thanks
    Thursday, May 24, 2012 2:00 PM
  • Hi Tom_Xu MSFT,

    I have tried various permuation and combination to get it work.

    But is there any standard way to for Addin

    1. MSproject-2007 (sp2) 32-bit.

    2. 64-bit machine

    What all I know is to make all project in solution specifically "64" bit.

    also make set up project TargetPlatform as "X64".

    Please let me know next steps.

    Thanks!

    Tuesday, May 29, 2012 9:40 AM
  • no, your add-in code should be anycpu and your installer target platform should match your office bitness (x86 here). To avoid publisher not verified window on first start after installation you can either make your plugin compile against .net 4.0 and install it into %programfiles% or you can add custom action to installer to add entry to inclusion list for vsto
    Tuesday, May 29, 2012 9:46 AM