SocketWrench 11

A general purpose TCP/IP component which makes it easy to quickly develop both client and server applications.

SocketWrench 11 TCP/IP Component


SocketWrench provides support for TCP and UDP sockets, and it can be used to quickly develop both client and server applications. Complex multi-threaded servers can be created with just a few lines of code, and TLS is built-in for secure connections.

Windows 11 and Server 2022

Supports Visual Studio 2022 and .NET 8.0

Secure Connections

Native libraries and C++ classes (32-bit and 64-bit)

ActiveX controls for Visual Basic 6.0 and VBA

Client and Server Applications

Product Overview

SocketWrench is a general purpose TCP/IP networking component designed to simplify the development of Internet client and server applications. Using SocketWrench, you can connect to virtually any service over the Internet, create your own custom servers, or integrate network functionality into your own software without being an expert in network programming.

SocketWrench includes managed .NET classes for Visual Basic and C#, ActiveX controls (OCXs) for use with languages such as Visual Basic 6.0 and dBase, and standard windows libraries (DLLs) for use with C++ and most other Windows programming languages.

SocketWrench is included within each of the SocketTools Editions but there has been an increased number of requests for SocketWrench to be made available as a separate product. As a standalone product, it is sold without our free support option, except for any Installation issues. Paid support options are available.

If in the future, you choose to purchase a SocketTools Edition, your SocketWrench purchase price will be applied as a credit on your SocketTools purchase. Here’s a description of everything included with SocketWrench.

SocketWrench ActiveX Control

The SocketWrench ActiveX control (OCX) is for development using languages such as Visual Basic 6.0, dBase and PowerBuilder. If you need to maintain legacy applications or prefer to use ActiveX components, SocketWrench offers a way to easily include Internet functionality in an application.

In addition to supporting standard network connections, SocketWrench also supports secure, encrypted connections using the industry standard TLS 1.2 protocol. As a lightweight ATL based control, SocketWrench has no dependencies on third-party libraries or the Visual C runtime, which means that there are no complex redistribution requirements.

SocketWrench Library and C++ Classes

The SocketWrench Library includes a general purpose TCP/IP library that can be used with virtually any programming language to create client and server applications. It provides an interface that is much easier to use than the standard Windows Sockets API, and includes integrated support for secure connections using TLS 1.2.

The Library Edition provides C++ classes, along with function declarations and constants for a variety of other languages, such as Visual Basic, Object Pascal (Delphi) and PowerBASIC.

SocketWrench provides high performance libraries with no external dependencies, and does not require COM registration. You can simply install them in the same folder with your application executable, without worrying about compatibility with other third-party libraries or additional redistribution requirements.

SocketWrench Support

A SocketWrench license includes free technical support by e-mail for installation issues and access to support resources such as our knowledge base and online help. Technical reference documentation and example programs are included with the product. If you have critical support needs, you can purchase additional support for your license.

Evaluate SocketWrench

You can download a free, fully functional evaluation copy of SocketWrench that you can use for 30 days. Your evaluation also includes free technical support when you have questions. After you have purchased a license, you can use the SocketWrench components in as many projects as you wish, and redistribute your software to an unlimited number of users, without any additional runtime licensing fees.


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)
Shopping Cart
Scroll to Top