Articles

SocketTools Lifecycle

The current version of SocketTools is 11.0.2148.1565 released on August 30, 2023. Technical support for version 10.0 ended on August 31, 2023. Earlier versions of SocketTools have reached their end of support. Upgrade pricing is available to developers who have purchased a SocketTools 10 or earlier license.

SocketTools .NET 8.0 Downloads

Microsoft released .NET 8.0 Preview 7 on August 8, 2023. It is the unification of earlier versions of the .NET Framework with .NET Core, enabling developers to use a single framework and runtime with uniform behavior supported on multiple platforms. .NET 8.0 will be released in November, 2023.

Using the SocketTools Test Server

When developing HTTP client applications using SocketTools, there may be situations where it’s useful to test your code, particularly with queries to web services. We have a server available for you to test various types of requests and see what the responses are in your code.

Referencing .NET Assemblies

SocketTools 11 includes assemblies which target .NET 4.0 through .NET 8.0. They are available as part of the standard installation package; however, you may need to reference them directly for new projects. This will always be required when building project using .NET 7.0 and later.

SocketTools .NET 7.0 Downloads

Microsoft released .NET 7.0 on November 8, 2022. It is the unification of earlier versions of the .NET Framework with .NET Core, enabling developers to use a single framework and runtime with uniform behavior supported on multiple platforms.

Visual Studio 2022 Released

Visual Studio 2022 was released on November 8, 2021. SocketTools 10 Build 1290 and later includes support for Visual Studio 2022 and .NET 6.0. Developers who have a SocketTools 10 license can update to the current version at no cost.

Comparing HTTP and FTP

The Hypertext Transfer Protocol (HTTP) and File Transfer Protocol (FTP) can be used to perform file transfers to and from the local computer to a remote server. SocketTools includes components for both protocols, and their interface was designed to make them interchangeable with one another.

Scroll to Top