jeep_xo
asked on
Break points
We are writing an App that uses ASP as the interface and VB for the Objects. Is there a way to set break points in the VB Object so that when a method is called from ASP we can step through the VB to find out where it's blowing up?
Hi you can set break point in the ASP using visual interdev by the result will be displayed only in the immediate and watch window. You must select the Debug / Process menu to select the browser file.
ASKER
It's fine to set the break point in Interdev except that on some of the ASP pages the only Jscript might be a single call to the VB Object. In this case I have no Idea where the VB has the problem. I know about binding IE to interdev through the debug/process menu. What I need is one step further... so we can step through the VB to see what's wrong. I realize we can set a form up in VB to test it there but periodically, what you think is being sent from ASP is not in the same form as what you tested in the VB Form.
maybe you could take the long way home and use msgboxes ..ie..
msgbox "I have " & var & " here!"
msgbox "I have " & var & " here!"
ASKER
That is what we are currently doing!
! always sounds angry for some reason!
Have a good one.
Wayne
Have a good one.
Wayne
ASKER
Didn't intend it to sound that way!!:-)
Yes, there is ...
- set your breakpoint
- start your dll (sounds strange but it makes the vbp the registered dll)
- make your asp-request
There are two requirements. You need to develop the vbobject on the machine your iis is on.
You have to be a fast debugger, otherwise your http-response will timeout...(but it's good enough for debugging if you get to the breakpoint and can step anyway.)
Nothing else is required.
Hope that helps.
PiN
- set your breakpoint
- start your dll (sounds strange but it makes the vbp the registered dll)
- make your asp-request
There are two requirements. You need to develop the vbobject on the machine your iis is on.
You have to be a fast debugger, otherwise your http-response will timeout...(but it's good enough for debugging if you get to the breakpoint and can step anyway.)
Nothing else is required.
Hope that helps.
PiN
ASKER
I set the break point...saved the files then built the DLL. It compiled fine but when I ran the ASP there was no difference. I tried again and left VB6 open at the break point. Nothing happened. Then I put a break point in interdev at the call statement and bound IE to it through the debugger. Stepped through the ASP...but no VB Objects.
No just leaving VB open .... start the dll too.
Leaving VB open doesn't help you.
Leaving VB open doesn't help you.
Are you there ?
I know it works...I have to do it every day.
;-)
- Set your breakpoint
- Press play in you VB-Project
- Request the calling asp
.... and there you go...
I know it works...I have to do it every day.
;-)
- Set your breakpoint
- Press play in you VB-Project
- Request the calling asp
.... and there you go...
ASKER
Sorry was in a planning meeting.
I have a form set up as an executable in the VB Project. Could this be the problem?
I have a form set up as an executable in the VB Project. Could this be the problem?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks PiN:
you've made life much easier for the other guys in my office. I unfortunately am Using W2K Server on my machine and NOTHING cool like that works on it. I should have stated that in my original question. All the guys using NT4 express their greatest thanks to you.
you've made life much easier for the other guys in my office. I unfortunately am Using W2K Server on my machine and NOTHING cool like that works on it. I should have stated that in my original question. All the guys using NT4 express their greatest thanks to you.
You're welcome. ;-)
Thanks for the points.
PiN
Thanks for the points.
PiN