how to debug classic asp and vb6 dll

purerandom

hi all, i am pulling my hair out here.
i have a classic asp website which creates an instance of a dll created in vb6.
i am developing in visual interdev 6, IIS 5, and microsoft visual basic 6.

now if i add a breakpoint to my asp code it steps through nicely and i can debug it. however what i want to do is for it to step into the vb6 function.

i have searched the net with no joy. i have both projects opened, i start the vb6 project as instructed which contains a breakpoint. i then start stepping through the classic asp page, but it never goes into the vb6 code.
Can anyone help me on this? any help would be great.

One other thing, is there any way i can attach the visual interdev to a process so that i can debug that way also. the classic asp site is called from a asp.net site so loads of session variables and the like are passed in.
i want to start debugging once it hits the asp site but again no joy!

any ideas?

Collumbo

i'm digging deep into the past here but i think this is how I did it:

I assume you are using a VB6.DLL, so that is the angle I will take here. If you are doing it a different way then I can't help.

debug it from the VB6 angle... in other words, run the VB6 code, and from there you launch your ASP page. When you open the VB6 code,

click Project menu
click <project name> properties
click debugging tab
select "Start browser with URL"
click ok...

Hit a break point in the first entry point in the code where you expect it to be called...

I'm curious to know if this works, but I do remember it being a pain the arse if you had an app which called a DLL in vb6.. you debugged one or the other, but not both at the same time.

amen

I find the best thing is
close any browsers, restart IIS, any com+ packages.

Open VB6. start your project in debug mode.

Open your asp solution in Visual Interdev/Studio (VS)

Navigate to your site.

In VS got to debug attach to process. Select the dllhost or inetinfo.

You should now be able to debug your ASP and VB 6

DonnieBrasco

i remember having to do this and eventually getting it to work.

The trick was to make sure that the compiled version of the dll was not loaded into memory. maybe even UN Register the compiled version / remove the actuall DLL from the pc.

You might try these steps

1 Set Web Services / IIS to be manual startup.

2 Reboot your station (IIS etc should not be running)

3 UN Register the compiled version / remove the actual DLL from the pc.

4 You need to make IIS have pretty much all the access possible on the directory where your vb code is. basically loosen up security around this folder as much as possible... make sure IIS user is part of an admin group etc.

5 While Web services /IIS is not running... start your code / insert a breakpoint somewhere relevant.

somewhere in the registry your project should under

HKEY_CLASSES_ROOT\CLSID\

which means its ready and waiting to be bound to.