Knowledge Base Articles

Windows and Supported TLS Versions

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.

Read More →

Resolving Compile and Link Errors

When you build your first C/C++ application using SocketTools, you may encounter compile or link errors. These are usually the result of the project needing to be configured with the correct paths for the required header files and import libraries.

Read More →

Supported Versions of Visual Studio

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.

Read More →

Support for TLS 1.2 on Windows XP

SocketTools uses the Windows CryptoAPI and Schannel security provider to provide support for Transport Security Layer (TLS), which is used with secure connections. The latest version of TLS that is available on the Windows XP platform is TLS 1.0 and cannot be used to establish secure connections.

Read More →

SocketTools 11 .NET Redistribution

When you create an application using the SocketTools .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 license key is not your product serial number. If you have an evaluation version of SocketTools, …

Read More →

SocketTools 11 ActiveX Redistribution

When you create an application using the SocketTools ActiveX Edition controls and you’re ready to deploy it, you must ensure the controls you’re using are initialized correctly. If you are developing with Visual Basic 6.0, and you’ve placed the controls on a form, it will automatically initialize the controls when the form is loaded. However, in some cases you must explicitly initialize the control, providing a runtime license key to …

Read More →

SocketTools and Catalyst Development have by far surpassed my expectations

I’ve been very impressed with all aspects of this project, and both SocketTools and Catalyst Development have by far surpassed my expectations. We ran into a number of roadblocks on this endeavor, and I appreciate your persistence and patience, particularly with the inconsistent test environment our client provided. I am also very impressed with the functionality of our new custom control. Very slick! Once again, thanks very much for all your hard work!
Kevin Taylor, Tailored Software, Inc. (Canada)

The documentation is amongst the best I’ve seen and used

Great product! I recently purchased the SocketWrench library and I’m pleasantly surprised by the ease of use and exceptionally intuitive API. I wanted to replace some home-grown code with the new component and it just dropped into place and worked on the first compilation! The documentation is amongst the best I’ve seen and used, with lots of clear and concise tips and helpful information. I am very impressed with the price-quality level. I look forward to many years of mutual benefits for both our companies.
Martin Hart, Memory Soft (Spain)

The best and most productive controls I have ever come across

Thanks for the amazing controls, the best and most productive I have ever come across. They work every time as per the detailed documentation with no gotchas. Great work.
Martin G Nagle, InfoMining PL (Australia)

I'm impressed with how you maintain backwards compatibility

I wanted to let you know how impressed I am with maintaining backwards compatibility. I had a VB6 program with 6 different implementations of the SocketWrenchCtl.SocketWrench class v4.5 (which was from 2006). I dropped the new in the updated .ocx file expecting to suddenly invoke 11 years worth of renamed properties, added dependencies and breaking changes. I have not yet changed a single line of code and so far (fingers crossed) it appears to be stable. I just thought I'd point that out because most devs can't go 3 months without introducing a breaking change (myself included)
Russell Phillips, Echotech (Australia)
Scroll to Top