Our knowledge base is a comprehensive resource designed to help you get the most out of our products. It includes getting started articles that guide you through initial setup, detailed information on specific features, and troubleshooting resources to assist you with any issues you may encounter. Explore our knowledge base to find helpful information about our products and answers to common questions.
IPWorks Bluetooth
Unix and Mac OS X: Exclude Unused Components During Compilation
04/30/2012 - Shows how to reduce the size of your compiled application by including only the components you need.
Using ASP.NET Components in a Medium Trust Environment
04/18/2012 - This KB entry includes instructions on how to configure a custom security level to allow the components to work in a medium trust environment.
SSH: Server
03/22/2012 - When attempting to connect, I get the error "Server
Using the Components in macOS and iOS
12/28/2011 - A Guide to Using the Components in macOS and iOS
Fixing COM class factory error 80040154 when using ActiveX controls in .NET Applications
06/24/2011 - How to fix the error "Retrieving the COM class factory for component with CLSID [ID] failed due to the following error: 80040154." when using ActiveX Controls in .NET applications.
Controlling browser behavior for S3 Objects in ASP.NET
04/22/2010 - Demonstrates how to control whether file content is displayed in a browser page or downloaded as a file in ASP.NET.
Optimize .NET DLL Load Time to Reduce Component Response Delay
04/21/2010 - When an internet connection is unavailable, .NET DLL load times may increase, causing components to respond slowly.
Ping: IPv6 support
07/01/2009 - IPWorks V8 supports using Ping with IPv6 addresses.
Delphi: Using the components in a Delphi package
06/30/2009 - This can be achieved following the steps below.
FTP Error: 550 SIZE Command Not Supported
01/13/2009 - This will occur when the component tries to calculate the percent complete for downloads.
Winsock Error 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
07/24/2008 - This is Winsock error 10060 which can occur for a variety of reasons.
Error Only one usage of each socket address (protocol/network address/port) is normally permitted
07/23/2008 - This occurs when more than one process attempts to bind to the same local port.