VS 2010 SP1 breaks add-in debugging targetting .NET Framework 2.0 rather than .NET Framework 4.0 - by Carlos J. Quintero

Status : 

  Duplicate<br /><br />
		This item appears to be a duplicate of another existing Connect or internal item.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 650694 Comments
Status Closed Workarounds
Type Bug Repros 7
Opened 3/10/2011 11:57:42 AM
Access Restriction Public


When you create a VS 2010 add-in that targets .NET Framework 2.0 rather than .NET Framework 4.0, and you set a breakpoint, it is not hit when you debug.

This didn't happen with VS 2010 without SP1 and this doesn't happen if the add-in targets .NET Framework 4.0.
Sign in to post a comment.
Posted by Bryan [MSFT] on 11/17/2011 at 5:17 PM
A KB article for this bug has been published on http://support.microsoft.com/kb/2591546.
And you can find the hotfix through the "View and request hotfix downloads" on the webpage.
Posted by eogas on 8/16/2011 at 9:13 AM
I just thought I'd mention that I just ran into this issue as well (with 3.5). A hotfix would be ideal.
Posted by Dan Attis [MVP] on 6/7/2011 at 12:03 PM
Just wanted to mention that this happens when targetting 3.5 as well, don't see it mentioned here.
Posted by Microsoft on 5/6/2011 at 5:12 PM
Hello again Carlos.

We're still looking into the right way to fix this bug. It's definitely an issue and is getting attention. Just thought you'd want to know we hadn't forgotten about this.


Matt Kaufman
Program Manager, Visual Studio Platform
Posted by Carlos J. Quintero on 4/3/2011 at 3:23 PM
Hello Matt,

While both workarounds works, I am not using them. I don't want to dirty the solution with a dummy project and I need to debug the add-in against several Visual Studio versions and re-targeting the .Net Framework is annoying. I think I will uninstall SP1 (it breaks other thing too).
Posted by Microsoft on 4/1/2011 at 4:07 PM
Hello again, Carlos.

At this time, we're still looking into the problem you're seeing to see if there is a better solution than the workarounds I posted. Did they work for you?


Matt Kaufman
Program Manager, Visual Studio Platform
Posted by Carlos J. Quintero on 3/26/2011 at 10:51 AM
Somehow SP1 broke this, is there any chance of a hotfix that restores this functionality that worked without the SP1?
Posted by Microsoft on 3/25/2011 at 3:03 PM
In order to debug add-ins built against .NET 3.5 or earlier, with Visual Studio 2010 SP1, you can

1.     Retarget your add-in to use the .NET 4.0 framework (via TargetFrameworkVersion) while you wish to debug it within VS 2010 or

2.     Use an Exe project in your solution to debug your 2008 addin, as follows:
a.     Choose "Add Project" and navigate to the version of Visual Studio that you wish to debug. For example, c:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe
b.     Right click on this project in solution explorer and set this project to be the Startup project. Also, set the Debugger type to “Managed v4.0”. This step is required and if not done, the addin breakpoints won’t be hit.
d.     Launch debugging session using F5

We are actively looking into better solutions for the next version of Visual Studio; sorry for the inconvenience.

Matt Kaufman
Program Manager
Microsoft Visual Studio
Posted by Microsoft on 3/24/2011 at 5:04 PM
We are looking into this.
Posted by Carlos J. Quintero on 3/17/2011 at 12:06 AM
VS 2010 SP1 RTM. I didn't tried the beta.

FWIW, other people have reproduced the issue too:

Posted by Reza [MSFT] on 3/16/2011 at 5:47 PM
Are you using VS2010 SP1 Beta or RTM?
Posted by Microsoft on 3/10/2011 at 7:21 PM
Thank you for reporting the issue.
We are routing this issue to the appropriate group within the Visual Studio Product Team for triage and resolution.These specialized experts will follow-up with your issue.
Posted by Microsoft on 3/10/2011 at 12:14 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)