Hiya,
I've heard that having standard modules in a VB ActiveX COM DLL is a security risk? The DLL's should only contain class modules?
Is this true? If so why???
Cheers!
Gaurav
Printable View
Hiya,
I've heard that having standard modules in a VB ActiveX COM DLL is a security risk? The DLL's should only contain class modules?
Is this true? If so why???
Cheers!
Gaurav
nah,
i think standard modules are fine... i mean how would you share for instance a global variable between 2 classes in the same DLL?
you need a standard module for that...
regards,
shizo
Does this have anything to do with hackers being able to inject code into the memory space of a dll loaded into memory?Quote:
I've heard that having standard modules in a VB ActiveX COM DLL is a security risk? The DLL's should only contain class modules?
Quote:
Originally posted by ShIzO
nah,
i think standard modules are fine... i mean how would you share for instance a global variable between 2 classes in the same DLL?
you need a standard module for that...
regards,
shizo
How about via a public property of an implemented class???