Leon94

Hello,

I've developed an AddIn on a machine (using the Addin Wizard) and found no problem to debug it within VS Studio 2005 IDE. This AddIn is not a COM.

When trying this very same AddIn on another machine, it's not possible anymore to enter AddIn code (breakpoints are not hit anymore). Code executed seems to be the compile version.

Did anybody encounter this problem before

Regards

Leon



Re: Visual Studio Extensibility Problem Debugging Add-In within VS IDE

Carlos Quintero - MVP

Is this an add-in for Visual Studio or a shared add-in (for Office) Also, are you trying to debug it remotely How have you set up that




Re: Visual Studio Extensibility Problem Debugging Add-In within VS IDE

Leon94

Hello,

I've tried with ToolWindow AddIn from "Microsoft Visual Studio 2005 Automation Samples".

I've followed the instruction:

Configuration is the following:

Application config:

Build output Path: MyDocument\Visual Studio 2005\AddIns

Debug config:

Start external program: C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\devenv.exe

Command line argument:: /resetaddin VBToolWindow.Connect

Working directory: C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\

Breakpoint is set in On: OnConnection Sub

Then I build the solution.

When launching the addin, Displays a new VS 2005 instance, I select new Windows application, go to Addin manager menu, Check "VBToolWindow Add-In", a dockable command button pops up but OnConnection breakpoint isn't hit.

Many thanks in advance

Leon





Re: Visual Studio Extensibility Problem Debugging Add-In within VS IDE

Carlos Quintero - MVP

Assuming that you start the new instance of VS 2005 debugging (F5) that can happen if the new instance is loading an add-in build that is not the one that you just built. So, ensure that the add-in registration (XML .AddIn file or registry) points internally to the build in your debug folder.






Re: Visual Studio Extensibility Problem Debugging Add-In within VS IDE

Leon94

The only "."Addin" file I've got is located in MyDocument\Visual Studio 2005\AddIns.

It's pointing to DLL file with no directly.

Is that a problem

Leon





Re: Visual Studio Extensibility Problem Debugging Add-In within VS IDE

Carlos Quintero - MVP

What do you mean with "DLL file with no directly"

Also, could you create a new add-in with the wizard and see if you can debug it (breakpoints are hit) If that works you could move the code of the other add-in to this one...






Re: Visual Studio Extensibility Problem Debugging Add-In within VS IDE

Leon94

Hello,

What I mean by Dll with no directory is the filename only with no path.

When I use the add-in Wizard for creating an AddIn all breakpoint are hit. This problem occurs for imported Addins only.

I already had to reconstruct an Addin with the Addin wizard in order to make the imported addin to hit breapoints. Is that the Microsoft procedure

Regards

Leon





Re: Visual Studio Extensibility Problem Debugging Add-In within VS IDE

Leon94

I found a thread very similar to mine on this forum:

Breakpoint will not currently be hit. No symbols loaded for this document posted by silentC Started: 14 Jul 2006 1:26 AM.

Take a look at it, I'm telling you, trouble ahead for debugging!

Leon





Re: Visual Studio Extensibility Problem Debugging Add-In within VS IDE

Carlos Quintero - MVP

AFAIK the .AddIn file should include the full path to the DLL file in your debug folder. You can edit it with a text editor.