Knowledge Base Articles
Building Visual C++ 6.0 Projects
When building a SocketTools project using Visual C++ 6.0 on Windows XP or later, make sure that you have installed Visual Studio 6.0 Service Pack 6 (SP6) and the Windows Platform SDK February 2003 Edition.
Read More →
Unable to Establish Security Context
An error is returned when attempting to create a secure SSL or TLS connection indicating that the SocketTools component cannot establish a security context. This error can occur for several reasons, depending on the server configuration and the version of Windows the application is running on.
Read More →
Connections Fail After Upgrading to Apache 2.4
Applications on unsupported versions of Windows may be unable to establish a secure connection to an Apache HTTP server after the server was upgraded to version 2.4. The same application was able to establish a secure connection with previous versions of the Apache server.
Read More →
Reference Manager Lists Multiple Assemblies
When adding a new reference to your Visual Studio project by selecting Project | Add Reference, or right-clicking on the project in the Solution Explorer, the Reference Manager will show multiple versions of the same SocketTools assemblies in the list.
Read More →
SocketTools Example Projects
SocketTools includes example projects for each edition as part of the standard installation. They are copied into the Documents folder for the current user who installs SocketTools. This will always be where the examples are installed, regardless of the path provided for the SocketTools edition you are installing.
Read More →
Invalid or Unsupported Authentication Protocol
When authenticating with an SMTP server using either the Authenticate method in the .NET class or ActiveX control, or when calling the SmtpAuthenticate function in the library API, the attempt fails with an error indicating an invalid or unsupported authentication protocol was specified.
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)