Distributing Custom SDK Applications

Custom solutions that are developed using the Visual Intercept SDK may be distributed though out your organization. If the custom solution is being installed on a machine that already has a Visual Intercept product, there are no additional distribution requirements other than components specific to your solution.

If the custom solution is being installed on a machine with no Visual Intercept product then there are additional installation components. If you are using an installer tool such as InstallShield, Wise, or Visual Studio you only need to integrate the viRuntime_3_6_0.msm merge module into your installer. The viRuntime merge module handles whether the files are shared as well as self-registering components. The merge module should handle all these issues.

If you are not using a formal installer that can work with merge modules then you should make sure the files listed in the manfest below are installed to the target client machine. These files should all reside in the same directory which would ideally be in the Program Files/Visual Intercept Enterprise directory.

The VisualIntercept.viEngine object is licensed. Object creation of licensed components is handled differently per implementation language. For Visual Basic, licensed components are handled automatically. For C++, the VisualIntercept.viEngine is created through the ILicenseFactory interface.

If you have other questions about issues not included in or beyond the scope of this Tech Tip, please contact Elsinore Technical Support Services at or 866.866.0034, option 2.