vb asp components

Binary compatibility allows the VB IDE to debug your component from within MTS.
Choose project properties --> Component --> binary compatibility.

André:cool:

Binary compatibility has nothing to do with debugging.... when no changes have been made to your components public interface... you choose binary compatibility to keep the component's signiture intact.. this is why we use the Binary compatibility option.. it allows other components referencing your objects to continue to communicate with them successfully... to test you component run the dll with a break point in the code (while in VB's IDE) and then run your ASP code... step through it using the F8 key.

Correction, if you do not have binary compatibility with the component you are trying to debug from within MTS, you will not be able to debug it!

Note also, that SetAbort does not work when debugging.

André

thank you

thank you

hi,
to debug a dll from asp what u do is unregister the dll or change the progid of the component and replace that progid with the previous one in ur asp.
run the dll by pressing f5 and keep a breakpoint in dll wherever required and it will stop there.

the constraint is that ur iis server, dll and ur asp should be on the same machine otherwise it would not work

this should help u

bye
Mustufa

Correction,

I'm not saying... that binary compatibility does not need to be set but in actuality this is not directly tied to debugging... it has to be set in order not to break compatibility (modify the component's signature). For example, I could late bind everything, test, and not even worry about setting this option..... I've done it.