Knowledge Base Articles
System.DllNotFoundException Error
When upgrading or deploying an application using one or more SocketTools .NET classes, an unhandled System.DllNotFoundException error occurs. A stack trace shows it is the result of a System.TypeInitializationException being thrown when the application first starts.
Read More →
Creating a Runtime License Key
To redistribute an application created using one or more SocketTools components, the application must initialize each component with a runtime license key. This is discussed in several places in the help, including the Licensing Information section, the Initialization section in the Developer's Guide and the initialization functions and/or methods in the Technical Reference. It is important to note that your serial number and the runtime license key are not the ...
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 →
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 ActiveX Redistribution
When you create an application using the SocketTools 11 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.
Read More →
SocketTools 11 Library Redistribution
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 your runtime license key is not your product serial number. If you have an evaluation ...
Read More →
5/5
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)
5/5
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)
5/5
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)
5/5
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)