People,
I have developed some components in VB which is the same used in an ASP
page.
Whatever, if I want to debug these components in a VB environment, it's very
simple because I create a project group and then add these component
project.
My question concerns about using Visual Interdev. Is there any way to debug
those components without creating it ?
Imagine if you have to make 10 modifications in the component... then, you
should compile the component 10 times ?!?

Thanks,
Fbio

Hi Fabio:

There are several ways to handle this without having build a physical DLL
each time the component is modified.

Here are 2 good ways.

(1)

Run the component in the VB IDE on the same machine, (in debug mode).

Put a break point in a called method in the VB code.

Run the ASP page on the same machine.

When the ASP calls the component, you will be able to step into the VB code.

Work with different settings for >Tools, >Options, >General, >Error Trapping,
to get the desired effect.

This is probably the best way to debug, but you cannot test transactioning
and load-handling.

(2)

Make changes to the VB component.

Build a new DLL.

Put the DLL into Component Services on the same machine.

Run the ASP on the same machine.

This will allow you to test transactioning, but you will not be able to step
into the VB code.

That's about it.

HTH

HAND

People,
I have developed some components in VB which is the same used in an ASP
page.
Whatever, if I want to debug these components in a VB environment, it's very
simple because I create a project group and then add these component
project.
My question concerns about using Visual Interdev. Is there any way to debug
those components without creating it ?
Imagine if you have to make 10 modifications in the component... then, you
should compile the component 10 times ?!?

Thanks,
Fbio