2

I've problem using visual studio 2010 on my computer (windows 7 64-bits)

I'm doing a c# add-in for outlook. I could add it on outlook, try it, but I couldn't debug it because debugger don't stop at breakpoints. I search something about that on google and here, but I found nothing that help me.

Someone have a solution ?

Improve this question

2 Answers 2

Reset to default
3

Have you attached Visual Studio to the Outlook process? To attach to an existing process open Debug->Attach to Process...

Then you should be able to debug your own code.

Edit: Have a look at this. Basically there seem to be two ways this could be resolved:

  • Change your project start action to Start Project instead of Start external app

  • There's another link in that article pointing to another post. In that is quite a lot of stuff, but at the bottom there's descriped that VS can't debug multiple Frameworks at the same time (like 2.0 and 4.0). There are also some descriptions at how to work around this.

Improve this answer
11
  • I couldn't do that. When I selected Outlook, "attach" couldn't be selected
    – Nanis
    Commented Feb 23, 2011 at 11:03
  • Is there already some debugger attached to outlook? I just had a quick look and could attach to any process on my system. Only time I know of that you can't attach is when the process already has a debugger attached. Have you checked the type of attachment? Default should be automatic, you can try setting it explicitly to managed.
    – Florian von Spiczak
    Commented Feb 23, 2011 at 11:08
  • Also if you are already attached to Outlook you have to make sure that the assembly used by Outlook is the exact same version you have in Visual Studio. VS won't break when the code base is different. Well, you can override this, but I forgot where exactly this option was. Anyway this usually won't help because different code bases make debugging nearly impossible most of the times.
    – Florian von Spiczak
    Commented Feb 23, 2011 at 11:15
  • In fact my problem is not to launch the debugger but that the debugger don't stop to the breakpoint. When I do "F5" outlook open with my add-in but never stop where i put break
    – Nanis
    Commented Feb 23, 2011 at 11:17
  • Ok, so you're already attached to outlook, that's good. Are you sure that line of code is executed? Maybe try some other line that is sure to be executed and see if that works. Also is the Breakpoint at runtime displayed normal or just lined out? If it's lined out it means either the assembly is not loaded yet or the CodeBase doesn't match. If the Breakpoint is outlined and your code is surely executed then have a look at the context menu for the breakpoint, I think there should be an option to ignore differing code bases.
    – Florian von Spiczak
    Commented Feb 23, 2011 at 11:19
0

I experienced this same issue in Visual Studio 2012.

I genuinely literally just added MessageBox.Show("test"); into private void ThisAddIn_Startup(object sender, System.EventArgs e) { } and the breakpoints that were already in existence were hit.

The cause of the original difficulty was the first time I experience an exception. Potentially the thread didn't exit cleanly and run auto generated finally and Shutdown methods.

Improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.