OK, I have now upgraded to the full Visual Studio 2013 package. I have selected Notepad as the external program for debugging. The EPDM Add-in is loaded into EPDM as a Debug-Addin.
I have added a break point in the GetAddInInfo procedure to verify if the addin is loaded correctly but when debugging the solution the execution is not stopped at the break point.
I have now added a messagebox in the GetAddInInfo procedure as another way to verify if the addin is loaded - and this messagebox is shown when running. So, the addin is loaded in EPDM.
So the problem is actually that VS doesn't stop at the inserted break points. I have found articles on the issue but none of the suggested solutions seems to work for me.
The good news is that the add-in is loaded but without break points it might get tough to debug the solution. It's not actually the answer to my original post but I will mark it so to close the case.
If anyone has suggestions to why my break-points are not working in VS - please let me know .
At some point I had found a short blurb indicating that EPDM needed MS Framework 2 to work. In Studio 2010 I went into properties>Compile>Advanced Compile Options>and changed the Target Framework to 2.
I cannot remember what changing the frame helped but this may be something you can try.
Thank you for your input Dan. I tried your suggestion but parts of my solution apparently requires a higher version of the Framework so it was not possible.
For different reasons I wanted to give my solution another name so today I have created a new project and moved the stuff from the old project. With the new project the execution stops at the inserted break points and I am now able to debug. I have NO idea why it works today...
I’m glad it is working. For future projects I found that if I use the working add-in as a template for new projects, it normally works fine, if I start a new add-in I will often have these problems again.
Good to know . Thank you!