SftButton/OCX 3.0 - Button Control

Distributing SftButton/OCX

This section describes the preferred distribution method when shipping SftButton/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 SftButton/OCX even if another vendor has already installed an application which also uses SftButton/OCX.

SftButton/OCX is not supported on Windows 95, 98, ME or Windows NT 4.0. Supported platforms include Windows 2000 through Windows 10 and their server editions.

Installing SftButton/OCX (for an Application)

When distributing SftButton/OCX with your application, only the following files can be distributed with your application royalty-free. These files allow the use of the control with your application. The design-time interface is no longer available once SftButton/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 SftButton/OCX installation directory (\Program Files\Softelvdm\SftButton OCX 3.0\Redist).

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

GDI+ (Optional)

Certain features of the control require GDI+ support. This is available automatically on Windows XP and above. GDI+ is available as a redistributable for Windows 2000 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.

Control 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\System32 directory (or Windows\SysWOW64 for 32-bit controls on Windows x64) directory is possible on all supported Windows platforms.

The setup program you provide with your application should install the SftButton/OCX control SftButton_IX86_U_30.ocx into the Windows System32 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 System32 directory.On Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 (R2) and Windows 8 it is usually named C:\Windows\System32 (or Windows\SysWow64 for 32-bit controls on Windows x64).

The control is installed into the Windows/System32 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 SftButton/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.

SftHelperComponent Target Directory

The SftHelperComponent (see "Using SftButton/OCX with .NET") is used by .NET applications. Earlier releases of SftButton/OCX required this component to be registered using Regasm.exe for COM Interop. This is no longer required. Simply copy the file Softelvdm.OCXHelperV2.dll (or Softelvdm.OCXHelper.dll) to one of the following locations. They are listed in the order they are searched.

Softelvdm.OCXHelperV2.dll:

• Same folder where the ActiveX control is installed (see Control Target Directory above)
• \Program Files\Common Files\Softelvdm\Softelvdm.Controls or \Program Files (x86)\Common Files\Softelvdm\Softelvdm.Controls (32-bit applications on 64-bit Windows versions only)
• \Windows\System32 \Windows\SysWow64 (32-bit applications on 64-bit Windows versions only)

Softelvdm.OCXHelper.dll:

• Same folder where the ActiveX control is installed (see Control Target Directory above)
• \Program Files\Common Files\Softelvdm\Softelvdm.Controls or \Program Files (x86)\Common Files\Softelvdm\Softelvdm.Controls (32-bit applications on 64-bit Windows versions only)
• \Windows\System32 \Windows\SysWow64 (32-bit applications on 64-bit Windows versions only)

The actual path (\Program Files or \Windows) may differ due to localization.

Version Control

The setup program should only install the SftButton/OCX files if the version number in the new files is higher than the files already installed. Maintenance releases 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 2.5, 3.0 and 3.5.

Reference Counting

When installing DLLs or OCX files into a "shared" location, such as the Windows\System32 or \Windows\SysWOW64 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 SftButton/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 SftButton/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 SftButton/OCX during the installation of your application. Please keep in mind that 64-bit versions of Windows have two versions of RegSvr32.exe. \Windows\System32\RegSvr32.exe is used to register 64-bit controls and \Windows\SysWOW64\RegSvr32.exe is used to register 32-bit controls. On Windows Vista and above, RegSvr32.exe must be run with elevated privileges as administrator.

SftButton/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 SftButton/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. Please keep in mind that an application using the LoadLibrary API can only load the control of the same machine type, meaning a 32-bit application can only load and register 32-bit controls, a 64-bit application can only load 64-bit 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 SftButton_IX86_U_30.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.SftButton30.Sample.exe" type="win32" />
 <description>SftButton 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="SftButton_IX86_U_30.ocx">
  <comClass description="SftButton/OCX 3.0 Button Control" clsid="{A65EEE94-0739-4116-8236-6DCAD56452B6}"
   threadingModel="Apartment"
   miscStatus="setclientsitefirst,alignable,actslikebutton,activatewhenvisible,insideout,cantlinkinside,recomposeonresize"
   progid="SftBtnATL30.SftBtn.1" tlbid="{A65EEE90-0739-4116-8236-6DCAD56452B6}"/>
  <typelib tlbid="{A65EEE90-0739-4116-8236-6DCAD56452B6}" version="3.0" helpdir=""/>
 </file>
</assembly>

Testing a Setup Program

If you test the installation of your application's Setup program on a system where the development version of SftButton/OCX is installed, you may notice that you can no longer use SftButton/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 SftButton/OCX. You can reinstate (or re-register) the design-time version of SftButton/OCX by using the program entry "Maintenance, Register SftButton OCX in Windows Registry" in the SftButton OCX 3.0 program group.