Quote:
|
Originally Posted by samar
What are the main benefits of using an interface over a referencing a .dll file directly?
How many interfaces can a VB class support?
What are the types of COM compatibility supported by VB6 (IDE)? Briefly explain the differences.
Thanks in Advance...
|
The main benefit of using an interface is that you don't need to write any code at all to use the functions exposed by the DLL. Since there is no code, if there are any changes to the DLL functionality you won't need to change anything in the classes code that uses the DLL.
A Visual Basic class can support two interfaces. One internal (to itself), one external (to other routines).
The com interfaces supported are
VB, and disorganized or DCOM. The
VB interface is suitable for supporting code written for a Virtual Branch (a tree structured form of distributed processing). The disorganized interface is suitable for dealing with spaghetti code written in other languages.
Just curious, but did you post the questions exactly as the instructor wrote them, or have you paraphrased them a bit?
-PatP