Re: Can't Debug COM Interface

Hello Oleg,

I finally can debug now. The problem was that the MFC Host application is
not loading the vb.net net dll directly but is starting up another exe file
that is loading the dll. if I specify the second exe as host application I
and then it works.

Thanks and Regards

Markus
"Oleg Starodumov" <com-dot-debuginfo-at-oleg> schrieb im Newsbeitrag
news:eAcmOmaHGHA.1728@xxxxxxxxxxxxxxxxxxxxxxx
>
> Hello Markus,
>
>> the debugger is set to CLR and Native, if I look into the registry the
>> path
>> to the DLL is also correct. When I start to debug the application the DLL
>> is
>> not copied to another location. For testing purposes I wrote in the
>> meantime
>> a com client in vb.net which is referencing the interface of the COM
>> Server
>> class. If I use this application as Host application I can debug without
>> problems. If I'm not including debug info in the client, the same
>> problem,
>> it's not possible to debug the server application. As the MFC application
>> also does not include debug symbols I'm not sure if debugging is possible
>> in
>> this configuration, or should this in general be possible what do you
>> think?
>>
>
> Debugging in this configuration is definitely possible.
>
> Could you please try the following steps and tell me what outcome you get:
>
> 1. Rebuild the VB.NET DLL (before rebuild, check that debug information is
> enabled
> and optimizations are disabled in build settings).
>
> 2. Open the MFC executable as a separate solution (File | Open Solution,
> open the .exe file),
> all subsequent steps should be done in this new solution.
>
> 3. In the project settings of this new solution, set the debugger type to
> "Managed only"
> (Project properties | Configuration Properties | Debugging | Debugger Type
> = "Managed Only")
>
> 4. Open a source file of the VB.NET COM component and set breakpoints in
> it.
>
> 5. Start debugging and make an action that should run the code where
> breakpoints are set.
>
> 6. If breakpoints are not hit, break into debugger (Debug | Break All) and
> open Modules window.
>
> 7. In Modules window, check the path to the VB.NET DLL. Is it correct?
>
> 8. Also in Modules window, check if symbols for the DLL are loaded.
>
> 9. If symbols are not loaded, R-Click on the module, choose Reload
> Symbols,
> navigate to the DLL's .PDB file and open it. Will symbols be loaded now?
>
> Oleg
>
>
>
>
>


.

Relevant Pages

  • Re: Cant Debug COM Interface
    ... When I start to debug the application the DLL is ... a com client in vb.net which is referencing the interface of the COM Server ... If I use this application as Host application I can debug without ... For debugging I can start the ...
    (microsoft.public.vsnet.debugging)
  • Error 430 driving me NUTS!!
    ... but this issue is causing my brain to short circuit (in addition to ... I have created an ActiveX dll and a test 'Container' application for it. ... debugging the dll, run the 'Container' and it worked. ... code just fine, but as soon as I closed down and try to debug, no go. ...
    (microsoft.public.vb.com)
  • Re: How to connect to children process
    ... Main problem is amount of manual operations required per debug cycle. ... connection to DLL with debugger takes sensible amount of time and manual ... Is the main problem that the debugger keeps symbols file loaded ... AFAIK that's how VS2003 debugger works, but WinDbg should usually ...
    (microsoft.public.vsnet.debugging)
  • Debug - Stepping through an exe without the source code - any help
    ... I am looking forward to learn how to debug exe or dll files without the ... source codes. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Design process using Windows Embedded CE 6.0, VS2005, CoreCon and SDKs
    ... This is unrelated to writing applications to run on the device, ... when the DLL or EXE ... Debug and test ...
    (microsoft.public.windowsce.platbuilder)
Loading