Re: Debug VS2005 .Net dll called from a VB6 exe

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Well if you only want to step in the error that occurs in the .Net dll then
the VB6 debug build isn`t even necesary

In my test environment the debugger pops up with a window in wich i can
select the sourcecode (of the .net assembly ) , it then breaks on the line
that raised the exception


hth

Michel





"Amelia" <Amelia@xxxxxxxxxxxxxxxxxxxxxxxxx> schreef in bericht
news:A520B653-32DF-4BBB-9B33-15F1BB0DA825@xxxxxxxxxxxxxxxx
THanks for your response Michel.

Just to calrify - so I need to acquire the pdb file and a debug build of
the
VB6 exe before i can attach to this process that then calls the .Net
program
of which I have the source?

Thanks

--
Kind Regards
Amelia


"Michel Posseth [MCP]" wrote:


Well you can atach to a process with the visual studio ide , so i if you
have the pdb file of the dll you can debug it with visual studio

regards

Michel Posseth [MCP]

"Amelia" <Amelia@xxxxxxxxxxxxxxxxxxxxxxxxx> schreef in bericht
news:E6DF4F45-AA47-4B33-9CD2-C9EFF79BEC21@xxxxxxxxxxxxxxxx
I only have a VB6 exe that calls a .Net "plug in" and only have the code
for
the plug in NOT the original exe but it needs to pass through all the
setup
com objects from the exe.

Should I be able to attach to this process and step into debug the .Net
code?

THanks

Milly





.



Relevant Pages

  • Visual Studio 2003 debug processes fails to see NET running in the IIS worker process (w3wp)
    ... Usually, to debug my .NET dll, I typically just run my web application ... attach to it via Visual Studio .Net, ... Yet, on the second machine, it was ...
    (microsoft.public.dotnet.general)
  • Re: debugging in asp.net and asp - urgent
    ... Are you receiving an instantiation error? ... I don't think you can debug into a .NET DLL even if you instantiate it ...
    (microsoft.public.dotnet.framework.aspnet)
  • Debug problem
    ... What I find particularly odd is that the exe created by the build seems to ... Debug Problems ... Then I got an idea and moved the exe to another folder on the ... the laptop. ...
    (microsoft.public.vstudio.general)
  • Re: .exe debug without sources from Visual Studio 2005
    ... >running WM 2003 SE using eVC 4.0 debugger with no problem. ... >that I want to debug that exe on another target device running Windows ... debugging unless the platform specified in the IDE matches the actual ...
    (microsoft.public.windowsce.embedded)
  • Re: properly disposing of filestream
    ... Try to use the release version of the EXE for the one app, and debug from VS the another instance. ... "The greatest danger for most of us is not that our aim is too high and we miss it, but that it is too low and we reach it" Michelangelo ...
    (microsoft.public.dotnet.languages.csharp)