debugging addins

[SomersetGraham]

Hi
I am trying to debug my addin -
I have tried attaching to a process and also setting the start up project to ea.exe.
Either way my breakpoints are not getting hit.

Can anyone tell me what I may be doing wrong

Thanks

[qwerty]

I always use the famous print statement to debug my add-ins. I also have a framework to run the add-in code externally. I simulate the GetTreeSelectedObject by a wrapper to supply a dedicated element.

q.

[Geert Bellekens]

It works for me, so you must be doing something wrong.
I always just attach Visual Studio/SharpDevelop to EA.exe and then it stops at my breakpoints.

What you could check
- Are you running your IDE as administrator (you should)
- Have you build your project in debug mode
- Have you build your project with "Register for COM Interop"

In general you have to make sure that the dll in your Project\bin\debug folder is the one that is used by EA.
You can easily test that by trying to delete it while EA is running. If you succeed then there's another dll that is being used.

Geert

[SomersetGraham]

Thanks for the replies

I am definitely obeying all of Geert's points but still no break points

I can display message boxes at the location I am trying to debug and they show up. but this is tedious at best

Anything else I could try?

[Helmut Ortmann]

Hi,

which edition of Visual Studio you are using?

If I remember right you need the professional edition for VS 2010 and later. Express doesn't work. There might be a workaround somewhere to get the express edition working for DLLs. Have a look in the community and this forum.

Helmut

[SomersetGraham]

I am using VS 2012
I just tried it on a colleagues machine and it works there so there must be something about my setup

[stao]

For VS2010 i have to do the following:

http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1295872058/8#8

I had a similar problem, but it boils down to the fact that if you start the EXE at debug time, VS2010 doesn't know what debugger to use, and it picks the wrong one!

To fix this, create an EA.exe.config file in the same location as EA.exe with this content:

<?xml version ="1.0"?>
<configuration>
 <startup>
   <supportedRuntime version="v2.0.50727" />
 </startup>
</configuration>


Now the start external program way of debugging works again.

~ Colin

[SomersetGraham]

Hi
Thanks for that
Unfortunately I still cannot debug by running EA from with VS 2012
However I am able to attach to a process

[Tehila1]

Hello!

I had a similar problem.
Try to use SharpDevelop free workspace instead of VSTO. This action solved my problem.

Hope this helps, please update.