Debug VS2005 .Net dll called from a VB6 exe

[Amelia]

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

[Michel Posseth [MCP]]

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" <Am****@discussions.microsoft.comschreef in bericht
news:E6**********************************@microsof t.com...

>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

[Amelia]

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" <Am****@discussions.microsoft.comschreef in bericht
news:E6**********************************@microsof t.com...

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

[Michel Posseth [MCP]]

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" <Am****@discussions.microsoft.comschreef in bericht
news:A5**********************************@microsof t.com...

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" <Am****@discussions.microsoft.comschreef in bericht
news:E6**********************************@microso ft.com...

>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