Distributing SftBox/OCX	Softel vdm, Inc.

This section describes the preferred distribution method when shipping SftBox/OCX with your application. This method follows Microsoft's guidelines on ActiveX control distribution. While these guidelines are not enforced, it is highly recommended that they are followed as outlined here. This insures that your application can be safely installed and use SftBox/OCX even if another vendor has already installed an application which also uses SftBox/OCX.

SftBox/OCX is not supported on Windows 95 or Windows NT 4.0. Supported platforms include Windows 98, Windows ME, Windows 2000, Windows XP, Windows Server 2003, Windows Vista and Windows Server 2008.

Installing SftBox/OCX (for an Application)

When distributing SftBox/OCX with your application, only the following files can be distributed with your application royalty-free. These files allow the use of the combo box control with your application. The design-time interface is no longer available once SftBox/OCX is shipped with your application. For additional information regarding distributing this control with your application, see the license agreement.

Required Files

Important: Redistributable files are located in the SftBox/OCX product directory (\Program Files\Softelvdm\SftBox OCX 4.5\Redist).

These files must be shipped with your application if SftBox/OCX is used:

File Name	Description
SftBox_IX86_U_45.ocx	Required. SftBox/OCX control.
Unicows.dll	Required for Windows 98, ME. It can optionally be installed on Windows NT, Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, but is never used. The DLL Unicows.dll can only be distributed under license from Microsoft Corp. This DLL can be downloaded at no charge from Microsoft's web site at http://www.microsoft.com/downloads/ searching for product "Platform SDK". The title of the item is "Platform SDK Redistributable: MS Layer for Unicode on Windows 95/98/ME Systems".
Softelvdm.OCXHelper.dll	Required for .NET ONLY. This .NET component is required when distributing managed .NET applications. It is not used for other (unmanaged) languages, like VC++, VB6, etc. This file must be registered for COM Interop during installation (e.g., using Regasm.exe or using the provided registry scripts Softelvdm.OCXHelper.Add.reg and Softelvdm.OCXHelper.Rem.reg).
Oleaut32.dll	Required. OLE support. While normally present, the installation must insure that the current version is installed. This file is also needed by the container (VB, VC++, etc.) to support OLE and any ActiveX control.
Olepro32.dll	Required. OLE property and standard types support. While normally present, the installation must insure that the current version is installed. This file is also needed by the container (VB, VC++, etc.) to support OLE and any ActiveX control.
Stdole2.tlb	Required. OLE support. While normally present, the installation must insure that the current version is installed. This file is also needed by the container (VB, VC++, etc.) to support OLE and any ActiveX control.
Asycfilt.dll	Required. OLE support. While normally present, the installation must insure that the current version is installed. This file is also needed by the container (VB, VC++, etc.) to support OLE and any ActiveX control.
Comcat.dll	Required. OLE support. While normally present, the installation must insure that the current version is installed. This file is also needed by the container (VB, VC++, etc.) to support OLE and any ActiveX control.
Regsvr32.exe	Optional. Control registration utility, for "manual" registration. Not needed with most commercial Setup creation tools.

GDI+ (Optional)

Certain features of the control require GDI+ support. This is available automatically on Windows XP, Windows Server 2003, Windows Vista and newer Windows versions. GDI+ is available as a redistributable for Windows 2000, Windows 98, and Windows Me from Microsoft (www.microsoft.com) as part of the Platform SDK (Windows XP and newer). Usually, it is sufficient to simply distribute the Dll gdiplus.dll in your application directory.

If GDI+ support is not available, the features are simply disabled and alternate presentation methods are used, if necessary.

Target Directory

Depending on the target operating systems, one of the following target directories can be chosen.

A) Windows\System(32)

Installing the ActiveX control into the Windows\System(32) directory is possible on all supported Windows platforms.

The setup program you provide with your application should install the SftBox/OCX control SftBox_IX86_U_45.ocx into the Windows System directory. The Windows System directory name can be found using the GetSystemDirectory API function.  All other files shown in the above tables also have to be installed into the Windows System directory.  On Windows 95, 98, ME, the Windows System directory is usually named C:\Windows\System or on Windows NT, Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008 it is usually named C:\Windows\System32.

The control is installed into the Windows/System(32) directory and registered using proper versioning and reference counting of the OCX file (usually automatic, with most commercial installers).  

B) Application Directory

An ActiveX control can be installed in the application directory using DLL/COM redirection, which is available on Windows 2000, 98SE and better only. 

DLL/COM redirection is activated on an application-by-application basis by the presence of a ".local" file. The ".local" file is an empty file in the same directory as the application's .exe file, with the same name as the application's .exe file with ".local" appended to the end of the name. 

For example, to activate DLL/COM redirection for an application called "SampleApp.exe", create an empty file called "SampleApp.exe.local" in the same directory where SampleApp.exe is installed.

On Windows XP or better, "Registration-Free Activation" (see below) can be used, which eliminates the need for the ".local" file.

Once DLL/COM redirection is activated, whenever the application loads a DLL or an OCX, Windows looks first for the DLL or OCX in the directory where the application's .exe file is installed.  If a version of the DLL or OCX is found in the directory where the application's .exe file is installed, the application uses it regardless of any directory path specified in the application or the registry. If a version of the DLL or OCX is not found in the directory where the application's .exe file is installed, the normal search path or server path is used.

Even if DLL/COM redirection is used, the control must be registered during installation (see "Registering SftBox/OCX" below).  The control must be installed into the Windows/System(32) directory and registered using proper versioning and reference counting of the OCX file (usually automatic, with most commercial installers).  In addition, a private copy in your application directory is always installed (but not registered), along with the application's ".local" file.

Version Control

The setup program should only install the SftBox/OCX files if the version number in the new files is higher than the files already installed. Maintenance releases and new versions of the product are fully upward compatible and are guaranteed to have a newer version number. New versions of the product will use new file names and new GUIDs so there will be no conflict between different (major) versions, such as 4.0 and 4.5.

Reference Counting

When installing DLLs or OCX files into a "shared" location, such as the Windows\System(32) directory, proper reference counting must be performed, to insure that the file isn't uninstalled until all applications making use of the DLL or OCX have also been uninstalled.  Reference counting is generally available with most commercial installers. The Windows Registry contains a count of all such shared files in the following Registry location:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs

Registering SftBox/OCX

Depending on the target operating systems, one of the following ActiveX/COM registration methods can be selected.

A) Windows Registry

Registering the ActiveX control in the Windows Registry is possible on all supported Windows platforms.

The setup program should register SftBox/OCX in the Windows registration database (Registry). This can be done manually using Regsvr32.exe which is discouraged. Many commercially available setup programs can register SftBox/OCX during the installation of your application.

SftBox/OCX is a self-registering ActiveX control. By using the LoadLibrary Windows API function, the GetProcAddress API can be used to obtain the DllRegisterServer function. By calling this function, the SftBox/OCX control will register itself with the Windows registration database (Registry). Most commercially available setup programs have support for this built-in. Check the documentation of your setup application for information on how to install ActiveX controls.

The following files need to be registered in this manner:

B) Registration-Free Activation

On Windows XP and better it is possible to deploy this ActiveX control using "Registration-Free Activation".  Registration-free activation allows distribution of the control without the requirement to register the ActiveX control in the Windows Registry (using REGSVR32 or a Setup application).  Registration-free activation is supported by the operating system, so the .NET run-time is not required for registration-free activation.

By using registration-free activation, true XCOPY deployment is possible.  Your application uses its own copy of the control.  Versioning, reference counting and registration of the control are completely eliminated and other installed versions of the control cannot interfere with your application.

By using an application manifest and copying the OCX file SftBox_IX86_U_45.ocx into your application directory, the ActiveX control is automatically registered when it is used the first time.  Your application manifest must include the comClass and typelib definitions shown below.  These insure that your application automatically registers the control and uses the control located in your application directory, regardless of any other controls or other versions of the same control already installed or in use.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly 
   xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> 
<assemblyIdentity version="1.0.0.0" processorArchitecture="x86" name="SoftelvdmInc.SftBox45.Sample.exe" type="win32" /> 
   <description>SftBox Sample Application</description> 
   <dependency>
     <dependentAssembly>
        <assemblyIdentity type="win32" 
             name="Microsoft.Windows.Common-Controls"
             version="6.0.0.0" 
             processorArchitecture="x86"
             publicKeyToken="6595b64144ccf1df"
             language="*" /> 
     </dependentAssembly> 
   </dependency>

   <file name="SftBox_IX86_U_45.ocx">
        <comClass description="SftBox/OCX 4.5 Combo Box Control"
                  clsid="{AD9B5C4A-4F77-4325-9EEB-F7E2B0583BCE}"
                  threadingModel = "Apartment"
                  miscStatus="setclientsitefirst,alignable,activatewhenvisible,insideout,cantlinkinside,recomposeonresize"
                  progid="SftBoxOCX45.SftBox.2"
                  tlbid = "{AD9B5C4B-4F77-4325-9EEB-F7E2B0583BCE}"/>
        <typelib tlbid="{AD9B5C4B-4F77-4325-9EEB-F7E2B0583BCE}"
                  version="4.5" helpdir=""/>
   </file>

</assembly>

Testing a Setup Program

If you test the installation of your application’s Setup program on a system where SftBox/OCX is installed, you may notice that you can no longer use SftBox/OCX in your development environment. This is caused by the fact that your Setup program installed a “run-time” only control on your system, which has replaced the “design-time” or development version of SftBox/OCX. You can reinstate (or re-register) the design-time version of SftBox/OCX by using the program entry “Maintenance, Register SftBox OCX in Windows Registry” in the SftBox OCX 4.5 program group.

Installing SftBox/OCX (for a Web Page)

When using SftBox/OCX on your web pages, only the following file(s) can be distributed royalty-free. These files allow the use of the combo box control on your web pages. The design-time interface is not available to visitors of your web site.

Required Files

Important: Redistributable files are located in the SftBox/OCX product directory (\Program Files\Softelvdm\SftBox OCX 4.5\Redist).

One of the following files is referenced by the OBJECT tag of a web page containing a SftBox/OCX control. This file must be available on your web server:

File Name	Description
SftBox_IX86_I_45.cab	Cabinet file containing the SftBox/OCX control, run-time only, compressed, with digital signature. This is the preferred method of including a combo box control.

Version Control

Version control is insured by using the proper HTML OBJECT (see Using SftBox/OCX with Internet Explorer, CODEBASE keyword). Maintenance releases and new versions of the product are fully upward compatible and are guaranteed to have a newer version number. Make sure to check the file Readme.html which was installed with SftBox/OCX for the most current version number to use.