Knowledge Base Articles
Runtime Error 424 Object Required
When executing a program that was created using Visual Basic 6.0 and a SocketTools ActiveX control, the following error is returned: Run-time error 424: Object required. This error can occur if the control is not properly registered on the local system, or if the object has not been referenced correctly.
Read More →
SocketTools 9 Installer Packages
SocketTools 9 includes Windows Installer (MSI) packages which enable you to easily redistribute the components used in your projects. They are included with the developer installation package for each edition and available for both 32-bit and 64-bit applications.
Read More →
SocketTools 9.5 Library Redistribution
When you create an application using the SocketTools 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.
Read More →
SocketTools 9.5 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.
Read More →
SocketTools 9.5 .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.
Read More →
Structured Data Over Stream Sockets
This article discusses several methods for exchanging structured messages over stream-based TCP sockets.
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)