Binary Compatibility

[C]

Hi,

Am new to world of COM.

When I compile COM DLL's what is teh fifference between
having theh dll as Binary Compatible as opposed to
Project Compatible?

Thanks,
C.

[solex]

[url]http://www.visibleprogress.com/vb_binary_compatibility.htm[/url]

"C" <c@nospm.com> wrote in message
news:0a8801c33fc5$fa7ae0d0$a101280a@phx.gbl...

> Hi,
>
> Am new to world of COM.
>
> When I compile COM DLL's what is teh fifference between
> having theh dll as Binary Compatible as opposed to
> Project Compatible?
>
> Thanks,
> C.

[Adrian Forbes [ASP MVP]]

> When I compile COM DLL's what is teh fifference between

> having theh dll as Binary Compatible as opposed to
> Project Compatible?

Ignore project compatibility and only use no compat or binary compat.

Binary compatibility means that you can compile your dll, then change the
code in it and re-compile the dll and any apps that reference your dll will
still work....ie it has maintained its identity. If you remove
compatibility then you get new guids etc created for your component and any
apps that need to use it need re-compiled against the new version of the
dll.

However...that is for any app that uses early binding. ASP uses VBScript
which can only use late-binding so, to be honest, it doesn't matter what
compatibility your dll has if it is only being called from ASP. Given that
no compatibility gives you no problems I'd use that if your dll is only
being used from asp.