SocketWrench 6.0 Licensing and Redistribution

The SocketWrench license permits the use of the library and/or control to build application software and redistribute that software to end-users. There are no restrictions on the number of products in which the SocketWrench library or control may be used. However, if SocketWrench has been installed with an evaluation license, any products built using it cannot be redistributed to another system until a licensed copy of the toolkit has been purchased.

System Requirements

SocketWrench is designed for the Windows platform, and is supported on Windows Vista, Windows Server 2003, Windows XP and Windows 2000. It is recommended that all platforms have the latest available version of Internet Explorer installed, along with all service packs and critical updates.

Windows Vista

SocketWrench is supported on the Windows Vista platform and requires that the operating system have all critical updates installed. It is strongly recommended that developers review the new guidelines for Vista published by Microsoft, including the new User Account Control (UAC) security system and its impact on applications. Note that because ActiveX control registration modifies restricted areas of the system registry, the controls must be installed and registered by an administrator with elevated privileges.

Windows Server 2003

SocketWrench is supported on the Windows Server 2003 platform and requires that Service Pack 1 (SP1) be installed with all critical updates. It is strongly recommend that you install Internet Explorer 7.0 which includes security updates for the browser.

Windows XP

SocketWrench is supported on the Windows XP platform and requires that Service Pack 1 (SP1) be installed with all critical updates. It is strongly recommended that you install Service Pack 2 (SP2) and Internet Explorer 7.0 which includes security updates for the operating system and browser.

Windows 2000

SocketWrench is supported on the Windows 2000 platform and requires that Service Pack 2 (SP2) be installed with all critical updates. It is strongly recommended that you install Service Pack 4 (SP4) and Internet Explorer 6.0 SP1 with all updates.

Earlier versions of the Windows operating system, including Windows 95, Windows 98, Windows Me, Windows NT 3.51 and Windows NT 4.0 are no longer supported by Microsoft. Using SocketWrench on an unsupported platform may require that the user install additional system components such as the Microsoft Layer for Unicode and the latest available version of Internet Explorer.

Library Redistribution

For those applications created using the SocketWrench library, the CSWSKAV6.DLL file must be distributed along with the application. The library has no external dependencies, other than standard Windows libraries that are part of the base operating system. In particular, the library does not use the Microsoft Foundation Classes library, nor does it use the Visual C Runtime library. If the SocketWrench C++ classes are used, then MFC support is required and must be linked into the application. Note that this is not a requirement for applications written in C or those applications written in C++ which do not use the SocketWrench classes.

Control Redistribution

For those applications created using the SocketWrench ActiveX control, the CSWSKAX6.OCX file must be distributed along with the application and the control must be registered by the installation program. The process of registration means that specific entries must be created in the system registry which provides information about the control such as the location of the OCX file. Fortunately, ActiveX controls are self-registering which means that the control has the ability to create or update those registry entries itself. To take advantage of this, the installation program must be capable of loading the control and calling those functions inside the control which update the registry. Most modern installation tools are capable of registering ActiveX controls. For in-house setup programs, refer to the technical article on ActiveX Control Registration on the Microsoft Developers Network CD.

It is possible to register ActiveX controls manually without the use of an installation program. This may be desirable in those situations where an application is being deployed internally or the developer does not want to create a setup program for a limited distribution. The tool used to manually register a control is named RegSvr32.exe and can be obtained from a number of places including the Visual Basic or Visual C++ CD-ROM. This utility accepts a command line argument which specifies the name of the control to register. For example:

C:>regsvr32 c:\windows\system32\cswskax6.ocx

A message box would be displayed indicating that the control was registered successfully. To prevent the message box from being displayed, use the /S option which tells the utility to function silently. If an error is reported, typically the reason is that a required system DLL is missing or out of date.

ActiveX control registration requires account elevation under Windows Vista because it modifies the system registry. To register controls from the command prompt, you must run it with administrative privileges. From the Start menu, select All Programs > Accessories and right-click on the Command Prompt item. Select "Run as Administrator" from the context menu that is displayed.

Version Information

The SocketWrench library and control have information embedded in them which provides version information to an installation utility. This information called the version resource, specifies the library or control's version number among other things. If you are using a third-party or in-house installation program, it is extremely important that the program knows how to use this information.

For example, if you are deploying an application which uses the SocketWrench library, the setup program must determine if that library has already been installed on the target system. If it has, it must compare the version resource information in the two libraries. It should only overwrite the library if the version that you have included with your application is later than the one installed on the system. An installation program which overwrites the library without checking the version number may cause other programs to fail unexpectedly on the end-user's system, which is obviously not desirable.

Library Installation Directory

It is recommended that you install the SocketWrench library in the same folder with the application that uses it. It is not recommended that you install the library under the Windows system folder. If you do choose to install the library in the Windows system folder, you must ensure that the installer makes the appropriate registry entries to indicate that it is a shared file. Failure to do so can result in the library being removed if the user uninstalls your application, which may cause other applications to fail.

ActiveX Installation Directory

The SocketWrench ActiveX control should typically be installed in the \Windows\System32 directory on the local machine. Some developers may prefer to install the control along with their application in a private directory. It is not recommended that developers take this approach unless COM redirection or registration-free activation is used because the full pathname of the control file is stored in the system registry when it's registered. If multiple applications install the same control in different directories, the actual control that will be used is the one that was last registered. This means that it is possible that an application will load an earlier version of the control than it was built with, which may result in unexpected or fatal errors.

COM redirection enables an application to isolate the controls that it uses, ensuring that the same version of the control which was used to build the application is loaded when the program is executed. To activate COM redirection, create an empty file named after the executable with a .local extension. For example, if the program is named MyProgram.exe then an empty file named MyProgram.exe.local should be created in the same directory as MyApp.exe. This binds the application to the local version of any controls which are installed in the same directory as the application. When an instance of the control is created, Windows will first search the application's directory, and then uses the standard search rules for locating the file. Note that COM redirection is not supported on Windows 95 or Windows 98.