Re: How can I prevent my public VB6 classes from being Implementable?
- From: "Jim Carlock" <anonymous@localhost>
- Date: Wed, 18 Oct 2006 22:16:54 -0400
"Joseph Geretz" <jgeretz@xxxxxxxxxx> wrote:
How do I prevent my public classes in my application DLL's from
being implementable?
An easy way would be to implement a key for each method call.
Then create a private function that checks to see if the key matches.
It means you'd have to place a call to the function inside some of
properties or procedures, preferably the ones that instantiate your
objects. If the key don't match you can exit the initialization event.
Another way involves setting a public key in your application and
then place the check in the Class_Initialize() event. This however,
means your app could be running and someone could instantiate
your objects.
There's other ways to accomplish your goals as well, but those
represent the initial thoughts that crossed my mind.
::::-o-::::
Jim Carlock
.
- References:
- How can I prevent my public VB6 classes from being Implementable?
- From: Joseph Geretz
- How can I prevent my public VB6 classes from being Implementable?
- Prev by Date: Re: How can I prevent my public VB6 classes from being Implementable?
- Next by Date: Re: How to change clsid when creating a VB6 ActiveX control
- Previous by thread: Re: How can I prevent my public VB6 classes from being Implementable?
- Next by thread: Re: How can I prevent my public VB6 classes from being Implementable?
- Index(es):