Compare SocketTools Editions

SocketTools .NET, SocketTools ActiveX, SocketTools Library, and SocketTools Subscription

The SocketTools Subscription combines all three editions, providing a single license for every .NET component, ActiveX control (OCX) and library (DLL) available for SocketTools.
Language / Toolset Subscription .NET Edition ActiveX Edition Library Edition
Visual C#
Visual C/C++
Visual Basic .NET
Visual Basic 6.0
Visual FoxPro
Office / VBScript
C++Builder
Delphi / Lazarus
PowerBuilder
PowerBASIC
FreeBASIC

SocketTools .NET Edition

The .NET Edition includes managed assemblies which can be used with Visual C#, Visual Basic .NET or virtually any other language which can target the .NET Framework. SocketTools includes assemblies for all of the current .NET Frameworks. Please note that .NET Core and .NET 5.0 are no longer supported by Microsoft, and it is recommended you upgrade your projects to a current version.

We will continue to include assemblies for legacy versions of the .NET Framework to assist with migration to a supported version. The minimum supported version is 4.0; however, we do have assemblies available for .NET 2.0 and .NET 3.5. The current Long-Term Support (LTS) version of the framework is .NET 6.0 which will reach end-of-support in November, 2024.

For Visual Basic developers, the SocketTools .NET components have an interface similar to the ActiveX Edition controls, simplifying the process of migrating legacy Visual Basic projects. Both the x86 and x64 target platforms are supported, or you can have your project target whichever platform your program is currently running on.

We support Visual Studio 2010 and later versions, including Visual Studio 2022. To use the .NET 8.0 Preview, you will need to install the Visual Studio 2022 Preview release. Microsoft is expected to release .NET 8.0 in November, 2023.

SocketTools ActiveX Edition

The ActiveX Edition includes ActiveX (OCX) controls which can be used with development tools and languages like Visual Basic, as well as Visual Basic for Applications (VBA) and scripting languages like VBScript. This edition includes both 32-bit and 64-bit controls (compatible with 64-bit versions of Microsoft Office) and can be used with most languages which support the ActiveX / COM standard.

We continue to provide support for Visual Basic 6.0 on modern Windows platforms and we have a similar interface to the .NET components. This can help with the transition from legacy Visual Basic development to the .NET platform. If you plan on migrating your projects to .NET, the SocketTools Subscription includes both .NET and ActiveX controls in a single license.

The .NET components have an interface that is similar to ActiveX Edition controls, simplifying the process of migrating legacy Visual Basic projects to Visual Basic .NET. Both the x86 and x64 target platforms are supported, or you can have your project target whichever platform your program is currently running on.

We support Visual Studio 2010 and later versions, including Visual Studio 2022.

SocketTools Library Edition

The Library Edition includes dynamic link libraries (DLLs) which can be used with C/C++ projects, including declarations for standard ANSI C along with C++ classes. It supports projects which use the Standard Template Library and ActiveX Template Library (ATL), as well as legacy projects which use Microsoft Foundation Classes (MFC).

The libraries have no external dependencies, does not require a specific toolset version, and doesn’t require you to use a specific version of the Visual C runtime. Visual Studio 2010 and all later versions are supported, and we also provide legacy support for projects being migrated from Visual C++ 6.0.

The Library Edition includes both 32-bit and 64-bit native libraries which can also be used with a variety of other programming languages like Delphi / Object Pascal. PowerBASIC and FreeBASIC. Because SocketTools uses similar calling conventions to the standard Win32 API, if your language is capable of calling functions exported from a dynamic link library, you can use the SocketTools Library Edition.

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