Results 1 to 8 of 8
  1. #1
    Join Date
    Nov 2003
    Posts
    3

    Unanswered: Debug set up on Interdev 6

    Hello,

    I'm a newbie in ASP. I have an ASP page that calls on a COM object. The COM code is failing at some point. Is there a way to configure Interdev so I can walk through the code, from the ASP to the COM object. Rather, the code will jump back and forth from the ASP to COM and vice versa. Thanks in advance!

  2. #2
    Join Date
    Nov 2003
    Location
    Christchurch, New Zealand
    Posts
    1,618
    Assuming your IIS server and your com dev machine is on the same box,... you should be able to start your vb com project running, which will create a temporary verson of the object. You asp pages should then link to that temporary object and you should be able to debug interactively... from memory...

  3. #3
    Join Date
    Nov 2003
    Location
    Christchurch, New Zealand
    Posts
    1,618
    Darn, got half way though this reply and missed something....

    I never had much success interactively debugging the asp itself though (I dunno if you can) but you can pop out debugging messages to dtermine where you are up to and the value of varriables and the like.

  4. #4
    Join Date
    Nov 2003
    Posts
    3
    Thanks rocslide, I'm still trying to get it to work. There seems to be some hooks missing because I'm not sure any more how to configure debug such that I can step through my asp and com code as if I was on one page or module of code. I'll let you know if I figure this out. Thanks again.

  5. #5
    Join Date
    Feb 2002
    Posts
    2,232
    Was the com object written in vb and do you have access to the source code ?

  6. #6
    Join Date
    Nov 2003
    Posts
    3
    Yes, the COM obj was in VB and I have both code on the same environment, different folders of course.

  7. #7
    Join Date
    Feb 2002
    Posts
    2,232
    Create a vb project that includes the com object - this is the simplest way to debug the com object.

  8. #8
    Join Date
    Feb 2002
    Posts
    2,232
    Or you can do the following:

    Open the com objects project - run the application (putting a breakpoint at the beginning of the code that is causing the problem).
    Open visual interdev - put a breakpoint in the asp page where the objects method is called.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •