Home > Troubleshooting > How to debug DXCore plug-ins under Visual Studio 2010 SP1

How to debug DXCore plug-ins under Visual Studio 2010 SP1

March 17th, 2011

Visual Studio Service Pack 1 introduced an issue that prevents breakpoints to be hit while debugging DXCore plug-ins. When you hit F5 to run the plug-in project, Visual Studio builds it and starts the second instance of Visual Studio where you can debug the plug-in. However, the breakpoints inside plug-in project won’t be hit when you have SP1 installed. The corresponding bug report is registered on the MS Connect. It seems that the issue is in the TargetFramework version set for the project: if the version is 2.0 – the break point won’t be hit.

Therewith, if you try to execute the “Break All” command, the following error appears:

Visual Studio error after Break All command

There are two workarounds for this issue:

  1. Manually attach to the debugging Visual Studio instance via the “Tools | Attach to Process…” menu item
  2. Change the TargetFramework version of the project to 4.0.

Let me know if you have issues with debugging of DXCore plug-ins under VS2010 SP1.

Products: all
Versions: 10.2 and up
VS IDEs: any
Updated: Mar/18/2011
ID: T043

Similar Posts:

  1. Karel Kr?l
    March 25th, 2011 at 01:43 | #1

    IMO changing the target framework to 4.0 does not work. I am debugging http://dxcorecommunityplugins.googlecode.com/svn/trunk/CodeIssueAnalysis/ (I am not an author, but there are some issues with this plugin)
    After I start debugging, I am getting

    System.ArgumentException crossed a native/managed boundary
    Message=Cannot find the requested resource.
    at Microsoft.VisualStudio.CommonIDE.ResourceLoader.FindResource[T](String resourceName, Int32 lcid, Func`2 fnConvert)
    at Microsoft.VisualStudio.CommonIDE.ResourceLoader.GetBlob(String resourceName, Int32 lcid, Byte[]& bytes, Int32& count)

  2. March 25th, 2011 at 05:42 | #2

    @ Karel Kr?l
    Thanks for joining in! I have downloaded the plug-in you mentioned, set the TargetFramework to the version 4.0 and I can debug it. I assume you have a different problem, something specific to your environment. I’ll let you know if I find any solution to the problem you noticed.

  3. June 28th, 2011 at 14:46 | #3

    Has this been resolved?

    I created a simple hello world pluggin and am still unable to debug/hit the breakpoint. In fact right now I have updated the plugin code and it is still running the old version of it? (how can i get it to use the most current code base)?


  4. June 28th, 2011 at 14:46 | #4

    Notify me

  5. June 29th, 2011 at 05:24 | #5

    The issue is registered on MS Connect, and it is not fixed at the moment. Have you tried to work around the issue? See the workarounds section in the article.