How can I prevent my public VB6 classes from being Implementable?
- From: "Joseph Geretz" <jgeretz@xxxxxxxxxx>
- Date: Wed, 18 Oct 2006 17:14:24 -0400
How do I prevent my public classes in my application DLL's from being
implementable? As it stands now, anyone could reference one of my
application DLL's, Implement its public class interfaces, and deploy a DLL
to 'masquerade' as one of my own application DLL's. With this approach,
anyone could get their hands on any internal application data passing across
a COM interface boundary. This doesn't seem very secure to me. (Or is what
I'm suggesting impossible?)
I know that it must be possible from a COM perspective to block unauthorized
implementation, since if I try to Implement ADODB.Recordset, for example, I
get the following error:
Compile error:
Bad interface for Implements: Interface is derived from another pure
interface with non-restricted methods.
To tell you the truth, I'm not sure what this means exactly, but the end
result seems to be that ADODB.Recordset is a public class interface which
can be accessed, but not Implemented. This is what I'd like to achieve for
some of my VB6 classes. Can this be done with VB6?
Thanks for your help!
- Joe Geretz -
.
- Follow-Ups:
- Prev by Date: Re: How to change clsid when creating a VB6 ActiveX control
- Next by Date: Re: Need simple code
- Previous by thread: Re: How to change clsid when creating a VB6 ActiveX control
- Next by thread: Re: How can I prevent my public VB6 classes from being Implementable?
- Index(es):
Relevant Pages
|