MSCOMCTL.OCX Could Not Be Loaded in VB6 Examples If one of the SocketTools VB6 example projects fails to open because MSCOMCTL.OCX cannot be loaded, the system typically has an older version of the Microsoft Common Controls library installed. This article explains why the error occurs, which controls are affected, and how to resolve the problem […]
MSCOMCTL.OCX Could Not Be Loaded in VB6 Examples Read More »
OpenSSL is an open source toolkit that implements the SSL and TLS security protocols. We have made Windows installation packages available for OpenSSL 3.5.6 which was released on April 7, 2026. This is the long-term service (LTS) release for the OpenSSL SDK which is supported until April, 2030.
OpenSSL Installation Packages for Windows Read More »
Apache Ignores Content-Length and Uses Chunked Encoding If you have a server-side script (CGI, FastCGI, mod_cgid, or certain PHP configurations) that explicitly sets a Content-Length header, you might reasonably expect Apache to pass that value through unchanged so the client can read exactly that many bytes and stop. This was the normal behavior for Apache
Apache Ignores Content-Length and Uses Chunked Encoding Read More »
Managing the Library Edition License Key This article explains how SocketTools Library Edition uses a runtime license key in applications, how the key is stored, and the recommended practices for managing it in source control and automated build environments. This is primarily oriented towards C/C++ developers, however the same general concepts apply to other languages
Managing the SocketTools Library Edition License Key Read More »
When you create an application using the SocketTools 11 Library Edition DLLs and you're ready to deploy it, you must ensure the libraries you're using are initialized correctly. This is done by providing a runtime license key to the initialization function for each of the SocketTools APIs you are using. It is important to note
SocketTools 11 Library Redistribution Read More »
The SocketTools .NET Edition includes assemblies which support several different versions of the .NET Framework and Visual Studio. When you add a reference to an assembly, make sure you are using the correct version which corresponds to the toolchain you are using to build your projects. When you install SocketTools, assemblies for each supported version
Visual Studio .NET Frameworks Read More »
When you create an application using the SocketTools 11 .NET Edition components and you're ready to deploy it, you must ensure it is initialized correctly. This is done by either providing a runtime license key to the Initialize method or setting the RuntimeLicense attribute for the executable assembly. It is important to note your runtime
SocketTools 11 .NET Redistribution Read More »
The Visual Studio releases supported by SocketTools 11 depends on the edition and languages being used. The following table lists which editions are compatible with Visual Studio and whether the edition is supported with that version.
Supported Versions of Visual Studio Read More »
SocketTools 11 components support all modern Windows desktop and server platforms. We recommend you install the latest security updates from Windows Update and the current network drivers available for your system. At this time, the only version of SocketTools eligible for technical support is SocketTools 11 Build 2130 or later. The following Windows desktop and
SocketTools System Requirements Read More »
SocketTools uses the Microsoft CryptoAPI and Schannel security package to implement support for secure connections using TLS. Which versions of TLS are available will depend on the version of the operating system you are using.
Windows and Supported TLS Versions Read More »
