Results 1 to 4 of 4

Thread: Debugging DLLs

  1. Dec 14th, 2001, 08:28 AM #1
    PunkRockNeil
    PunkRockNeil is offline

    Thread Starter
    Lively Member
    Join Date
    May 2001
    Location
    Fredericton, NB, Canada
    Posts
    85

    Debugging DLLs

    I was wondering if anyone could help me with debugging visual basic dlls when they're being used by a web application.

    Thanks,
    Neil
    Reply With Quote Reply With Quote
  2. Dec 14th, 2001, 09:42 AM #2
    FATBOYPEE
    FATBOYPEE is offline
    Hyperactive Member FATBOYPEE's Avatar
    Join Date
    May 2001
    Location
    Charleville (Ireland) Still. ANYONE GOT A JOB I CAN HAVE ? GIZA JOB. I CAN DO THAT....
    Posts
    463
    The DLL is deployed ??? Or are you talking debugging the VBP that will make up the DLL ?

    If it's the former, then you will need to change the DLL to write an output file to the server & append it with any error messages or warnings.

    If it's the latter, then with Visual Studio it's a nightmare, without Visual Studio, its impossible.....(IMHO)....

    Pee

    Best Bar.....
    Reply With Quote Reply With Quote
  3. Dec 15th, 2001, 09:57 AM #3
    PunkRockNeil
    PunkRockNeil is offline

    Thread Starter
    Lively Member
    Join Date
    May 2001
    Location
    Fredericton, NB, Canada
    Posts
    85
    It is indeed deployed. A person I work with told me you can set breakpoints within the code and that they would stop at these breakpoints even when the dll is deployed. It doesn't sound right to me, but I was taking his word on it and now he's started christmas vacation so I have no idea how to approach it...
    Reply With Quote Reply With Quote
  4. Dec 17th, 2001, 03:37 AM #4
    FATBOYPEE
    FATBOYPEE is offline
    Hyperactive Member FATBOYPEE's Avatar
    Join Date
    May 2001
    Location
    Charleville (Ireland) Still. ANYONE GOT A JOB I CAN HAVE ? GIZA JOB. I CAN DO THAT....
    Posts
    463
    There's no way you can set any breakpoints within the code after compliation (least never heard of that !!!), if you want error output that you can read etc then your best method is to build an error handler which writes to a file information aobut the error : procedure in which it occurred, date/time it occurred & the specific err number & description.

    Pee

    Best Bar.....
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

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

Forum Rules


Click Here to Expand Forum to Full Width