|IMG Developer's Kit: Developer's Kit Guide and Technical Documentation; Version 1.79; User's Guide|
|Prev||Chapter 2. Developer's Corner||Next|
How Do I register / move the DLL?
Visual Basic Developers: Review the samples in the VBASIC folder (Installed Developer's Kit) for Form Event Examples, and Module Load information - This is the starting point for integrating into VB! (Note: MTSDLL is the future of this DLL (1.71 Release))
Question: How do I Register the DLL?
Answer: You don't - the DLL is a Dynamic Link Library of Compiled (Native C) code - by declaring the Module "Lib" statements, you are indicating to your VB Project where to find the DLL. This question arises because VB developer's are familiar with COM Components located in a DLL which need to register the Server that handles the interface to these COM objects. The MTSDLL is not like a COM Component in a DLL. The C-based DLL is a lot more direct, quicker, with no overhead, and what optimized computer software is all about - do the job intended with minimal impact on system performance.
Several quick notes:
( 1) You have the source code
( 2) Think from your programs point of view: Calling the function (with the "Lib" statement required in the module) is more straightforward than reviewing all of the registered system components to find if a particular capability is available - if you've ever waited for Windows to load, you may appreciate the speed, power, and directness of using only what you need.
( 3) If you move the DLL, you will need to update the "Lib" statements to indicate its location - also, see below.
( 4) There are advantages and disadvantages of using COM components and advantages and disadvantages of using C-based DLL's. This is a C-based DLL.
( 5) If you want to build this functionality as a COM interface that adds layers of complexity, takes time, taps system performance, and provides no further functionality, you have the source code.
Question: How do I move the DLL?
Answer:You may move the DLL anywhere on the system, but please note the following items:
( 1) If you move the DLL, you will need to update the "Lib" statements to indicate its location.
( 2) If "hard coding" the location is not desirable, you may simply enter the name of the DLL, e.g. "MTSDLL.DLL" and move the DLL into a location indicated in your environment's path. Although not recommended, you can drop the DLL into the "\WINDOWS\SYSTEM" ("\WINNT\SYSTEM32") folder. If unfamiliar with these issues, please refer to Microsoft documentation on Windows and the Visual Basic reference.
( 3) If you don't know your project's location, you can use the "\Program Files\Common Files" area and create your own spot for your program's required files.
( 4) Refer to the "Load" event of the example projects - use the Dir command to verify the DLL is located where you expected it, or exit gracefully.
( 5) Refer to Microsoft Help for VBA on DLL's and locating them.
( 6) Refer to Microsoft Knowledge Base Q106553 for notes on integrating C based DLL's and Visual Basic.
|How do I implement "on-demand" use with Visual Basic/MS Access?||Up||How do I Integrate with Internet Explorer|