Search the web
Sign In
New User? Sign Up
vsnetaddin · Visual Studio.NET Add-ins
? Already a member? Sign in to Yahoo!

Yahoo! Groups Tips

Did you know...
Want your group to be featured on the Yahoo! Groups website? Add a group photo to Flickr.

Best of Y! Groups

   Check them out and nominate your group.
Having problems with message search? Fill out this form to ensure your group is one of the first to be migrated to the new message search system.

Messages

  Messages Help
Advanced
HELP: I can no longer debug my add-in (VS.NET 2003)   Message List  
Reply | Forward Message #3833 of 3878 |
I've been writing a VS .NET 2003 add-in for some time now and have
recently lost the abillity to debug my add-in.

I've tried uninstalling and re-installing my add-in using the generated
setup file and I've tried re-creating the commands.

For some reason whenever I try to debug my add-in the second instance
of Visual Studio runs but my add-in code is not loading, i.e. any
breakpoints set in the OnDisconnection method has the warning "The
breakpoint will not hit. No executable code is loaded at the current
location" (even though the add-in has clearly loaded in the second
instance of VS).

It seems as if the add-in being loaded is a different dll to the one
I'm trying to debug.

As anyone got any suggestions?

TIA




Tue Nov 27, 2007 12:33 am

thenybbler
Offline Offline
Send Email Send Email

Forward
Message #3833 of 3878 |
Expand Messages Author Sort by Date

I've been writing a VS .NET 2003 add-in for some time now and have recently lost the abillity to debug my add-in. I've tried uninstalling and re-installing my...
Tim
thenybbler
Offline Send Email
Nov 27, 2007
12:41 am

Did you check the registry to make sure the entries for your add-in are located where the registry thinks they are? ... From: Tim To:...
greeneyes
starthefish
Offline Send Email
Nov 27, 2007
2:55 am

I've not changed any of the registry settings - and debugging had been working for months. It seems like VS is loading a different version of my addin's .dll....
Tim
thenybbler
Offline Send Email
Nov 27, 2007
9:56 am

Hi, 1. Check whether on the project properties you have enabled the "Enable the unmanaged code debugging". 2. Under project properties goto Build tab and check...
Shah Japan
shahjapan
Offline Send Email
Nov 27, 2007
1:55 pm

I've checked that Unmanged Code Debugging is enabled and that Register for COM Interop is enabled. I've also checked that .NET Framework SP1 is installed...
Tim
thenybbler
Offline Send Email
Nov 27, 2007
8:23 pm

I've now solved the problem - it was being caused by VS .NET somehow loading the Release version of my dll not the Debug version. I manually removed all...
Tim
thenybbler
Offline Send Email
Nov 27, 2007
10:53 pm
Advanced

Copyright © 2009 Yahoo! Inc. All rights reserved.
Privacy Policy - Terms of Service - Guidelines - Help