locked
Problems with migrating Add-in from Visual Studio 05/08/10/11 developer preview to 11 beta. RRS feed

  • Question

  • I have been developing an Add-in for Visual Studio and have working versions for Visual Studio 2005, 2008, 2010 and 11 Developer Preview. However, although the installation runs fine on Visual Studio 11 Beta, the Add-in does not show up. Anyone know what has changed between the developer preview and beta that might cause this?
    Friday, March 9, 2012 1:12 AM

Answers

  • Are you running "devenv /setup" at the end of your install? That's now a requirement in VS 11.

    Thanks,
    Aaron


    http://blogs.msdn.com/aaronmar

    Friday, March 9, 2012 4:43 PM

All replies

  • When you say 'does not show up' do you mean it doesn't load/run or it isn't even showing up in the AddIn Manager dialog?

    Ryan

    Friday, March 9, 2012 1:42 AM
  • Hi "Addin Dev",

    Where are you installing your Addin to?

    Regards,
    Aaron


    http://blogs.msdn.com/aaronmar

    Friday, March 9, 2012 2:24 AM
  • Ryan: Does not even show up in the AddIn Manager Dialogue.

    Friday, March 9, 2012 2:54 AM
  • Aaron: I am not sure which detail you are asking...

    Installing files to: [ProgramFilesFolder]\[Company]\[Software], e.g. C:\Program Files (x86)\Company\Addin version 1.1.1\file.ext

    Registry entries root: \Software\Microsoft\VisualStudio\11.0

    Adding menu at the top with commands and adding a couple of buttons to the standard toolbar.

    Or are you asking something else?

    Friday, March 9, 2012 3:10 AM
  • Are you running "devenv /setup" at the end of your install? That's now a requirement in VS 11.

    Thanks,
    Aaron


    http://blogs.msdn.com/aaronmar

    Friday, March 9, 2012 4:43 PM
  • Hello Aaron,

    Really? We are talking about add-ins (not packages), which never required devenv.exe /setup and certainly I have run add-ins on VS 11 Beta without such step...

    Best regards,

    Carlos


    MZ-Tools: Productivity add-ins for Visual Studio: http://www.mztools.com. My blog about developing add-ins: http://msmvps.com/blogs/carlosq/

    Friday, March 9, 2012 6:46 PM
  • Hello,

    See:

    How to ask questions to increase your chances of an answer
    http://social.msdn.microsoft.com/Forums/en-US/vsx/thread/9307ca0b-d152-4c31-85f5-05b6166d7410

    Nothing has changed in VS 11 Beta or VS 11 Developer Preview, so there must be something wrong on your side.

    Can you post the following:

    1) The path to your .AddIn file (that you are using to register your add-in inside the Add-In Manager)

    2) The contents of your .AddIn file

    3) A screenshot of the  "Tools", "Options" window, "Environment", "Add-in Security" section to see which paths your VS 11 is using to locate .AddIn files

    Without that information I can only recommend to take a look at the following articles:

    INFO: Default .AddIn file locations for Visual Studio add-ins
    http://www.mztools.com/Articles/2008/MZ2008001.aspx

    HOWTO: Using the Process Monitor (ProcMon) tool to diagnose Visual Studio add-ins problems
    http://www.mztools.com/articles/2008/MZ2008024.aspx


    MZ-Tools: Productivity add-ins for Visual Studio: http://www.mztools.com. My blog about developing add-ins: http://msmvps.com/blogs/carlosq/

    Friday, March 9, 2012 6:55 PM
  • For XML addins, they shouldn't require "devenv /setup". However, for COM addins that register under HKLM\Software\Microsoft\VisualStudio\11.0, yes, they will have to run "devenv /setup" to trigger a pkgdef merge on the next startup.

    Regards,
    Aaron


    http://blogs.msdn.com/aaronmar

    Friday, March 9, 2012 7:09 PM
  • Hi Aaron,

    This (sort of) resolves the issue. I haven't incorporated it into the installer yet, but running "devenv /setup" manually makes the addin appear. Unfortunately the output from running "devenv /setp" is "The operation could not be completed"...

    Posting this now to let you know. Will edit/update once I have tried putting "devenv /setup" into the installer itself.

    Edit/Update:

    The installer was calling "devenv /setup", however due to Visual Studio 11 being beta the installer software was ignoring the call/doing nothing. This apparently worked fine for the developer rpeview, but not for beta. Running manually around it is a hack for now until the installer is fixed.

    Sunday, March 11, 2012 11:22 PM
  • Are you running "devenv /setup" with Administrator permissions?

    http://blogs.msdn.com/aaronmar

    Monday, March 12, 2012 2:12 PM