RE: VS 2005 won't hit breakpoints when debugging an executable

Hello Steve,

From your description, you're debugging an exe application which reference
a separate managed assembly. Since you've the debugging info (symbol and
source) of the assembly, you want to perform source code debugging against
the class library assembly. However, you found the debugging has some
problem(break point not hit) in VS 2005 while it works in VS 2003, correct?

For the exeutable, is it also an .net managed application or an unmanaged
application that use interop to call the managed class library assembly?
If it is a managed application and it is originally built under VS
2003/.NET 1.1, you need to rebuild it with VS 2005 under .net framework
2.0. Is this the case? Or if both the exeutable and dll are unmanaged
binary?

Please feel free to let me know if there is anything I missed here.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead



==================================================

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.



Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.

==================================================



This posting is provided "AS IS" with no warranties, and confers no rights.



.

Relevant Pages

  • RE: VS 2008, IIS and Vista debugging
    ... While you are performing the debugging on the Asp.net application under ... There may be some problem of launching "Protected Mode" of IE7 for Asp.net ... Microsoft Online Community Support ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.vsnet.debugging)
  • Re: Step Over (F10) and Step Into (F11) also show assembler code
    ... Today if I step through with F10 and F100 it works as it should. ... debugging, Enable Address-Level debugging and Show disassembly if source is ... Microsoft Online Community Support ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.vsnet.debugging)
  • RE: Step Over (F10) and Step Into (F11) also show assembler code
    ... created a console type in VS2005 to test your scenario. ... debugging, Enable Address-Level debugging and Show disassembly if source is ... Microsoft Online Community Support ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.vsnet.debugging)
  • RE: VS2005 Break Point Bug?
    ... it is not possible to remove break point when debugging. ... the problem is you remove a breakpoint in a web ... Microsoft Online Community Support ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.vsnet.general)
  • Re: Customizing the output of CTRL-T
    ... There has been some discussion of using Guy's feature for debugging. ... similar commands to the VMS debugger for language support. ... If you have received the email in error, please notify TransGrid ... individual sender except where the sender expressly and with ...
    (comp.os.vms)
Loading