Version: 4.4.7.0
Add secure Telnet, rsh, rexec and rlogin connectivity to any .NET application or service.
Product Release History
The following is a list of public releases for all components shipped with PowerTCP Telnet for .NET (Latest Release 2017-03-09)
PowerTCP Telnet for .NET
Current Version: 4.4.7.0
4.4.7.0    Released: 2017-03-08
  • Visual Studio 2017 compatibility.
4.4.6.0    Released: 2016-12-19
Product fixes in this release:
  • Login prompt exception messages have been improved and will now report which prompts could not be found.  (655)
4.4.5.1    Released: 2012-11-15
  • Changed serialization to use simple partial name serialization to improve cross-version compatibility.
Product fixes in this release:
  • Addressed issues in the sample Telnet model code that caused an exception to be incorrectly thrown during the login process.
  • Addressed an issue where the control might hang if the remote server closes the connection during a read with the Telnet control.  (5446)
  • Addressed an issue where calling the Close method on the Telnet control in the StateChanged event may cause the Telnet control to hang.  (5631)
4.4.4.5    Released: 2012-10-24
  • Updated for Visual Studio 2012 integration and Windows 8 compatibility.
  • Trial licensing operation updated.
Product fixes in this release:
  • Addressed a globalization issue that prevented correct operation for systems using the following language cultures: Azeri (az), Azeri-Latin (az-Latn), Azeri-Latin-Azerbaijan (az-Latn-AZ), Turkish (tr), Turkish-Turkey (tr-TR)  (TFS31)
4.4.3.1    Released: 2012-07-12
Product fixes in this release:
  • Fixed a licensing issue with web service applications.
  • Updated the title bar of licensing messages to not indicate a product is in trial when it is licensed.
4.4.2.0    Released: 2012-06-27
  • Updated trial operation behavior and removed obstacle to using product in .NET Framework 4.5.
4.4.1.1    Released: 2012-04-30
Product fixes in this release:
  • Fixed an issue that prevented operation in MONO. A NotImplementedException no longer occurs when trying to connect in a MONO environment.  (5586)
4.4.0.2    Released: 2011-03-24
  • Some custom Start delegates have been replaced with the .NET Framework standard WaitCallback delegate. This generally means that callback functions no longer include the calling component as a parameter (this is true even for custom delegates that were not replaced).
  • The Connect method was updated to take the new TcpSession object as a parameter. TcpSession is a serializable object that facilitates the saving of session settings.
  • The AuthenticateAsClient and AuthenticateAsServer methods were updated to take the new ClientSecurity and ServerSecurity objects as parameters, respectively. These two objects are serializable, facilitating the saving of security sessions.
  • The ReadToX functions (ReadtoDelimiter, ReadToCount, ReadToEnd) were updated to throw the new DataException when an error condition occurs. DataException includes a DataRead field which provides the data read prior to the exception.
  • Several samples were updated with "model" classes, to fall more in line with the Model-View-Controller (MVC) design philosophy. For more on MVC, see the "MVC Design in Applications" page of the help file.
Product fixes in this release:
  • Fixed an issue where the components would not use a specified local port under certain circumstances.  (5359)
4.2.1.1    Released: 2010-05-14
  • PowerTCP Telnet has been updated with a new install and VS 2010 integration.
Product fixes in this release:
  • Fixed a delay that would sometimes occur during the first Connect to a server.  (5118)
  • Data Direction in the Log event handler has been fixed to no longer always be DataDirection.In.  (5169)
  • The behavior of the Login method has changed. The default timeout value for each Read is now 6 seconds. A timeout exception will occur if the expected login prompt or password prompt is not found before the timeout period expires.  (5216)
  • Aborting an explicitly secure connection during the SSL Handshake no longer negatively impacts an immediate subsequent explicitly secure connection.  (5275)
4.2.0.1    Released: 2010-01-05
  • Telnet for .NET now uses native Framework classes for SSL functionality.
  • Telnet for .NET has a new licensing model. External runtime license files are no longer utilized. Instead, a license resource is generated and embedded within the executing assembly.
4.1.2.0    Released: 2009-10-30
  • An update to licensing and the help file. Note that users with an existing 4.1 Developer License File must obtain a new Developer License File for this release.
4.1.1.0    Released: 2009-06-03
  • An update to licensing and the help file.
4.1.0.0    Released: 2009-05-13
  • The component Error event handler now utilizes Dart.Common.ComponentErrorEventArgs.
  • Telnet has been updated with a new easier-to-use licensing model.
4.0.0.1    Released: 2009-02-17
  • This latest version of the venerable PowerTCP product line gets a new .NET 2.0 re-design that leverages the power of the latest .NET environments to provide the most advanced Internet Communications components available. Some of the features include:
  • Auto-login capabilities
  • Auto-option negotiation with easy configuration options
  • Secure SSL Telnet support
  • Blocking reads that wait for defined delimiters, specifically designed for scripting applications
  • Start method for easily implemented multi-threaded applications, including cross-threading marshaling support
  • PTY property binds a TextBox to the Telnet component as a ready-made interface for interactive online communications
  • Logging event for easy debugging and session logging
  • Proxy support
  • Includes Rexec, Rsh and Rlogin components in addition to Telnet
1.0.6.0    Released: 2007-07-06
  • Sample applications are now included for .NET 1.1 and 2.0. Samples for .NET 1.0 are no longer shipped.
Product fixes in this release:
  • Under .NET 2.0 only, a blocking socket receive() can generate a timeout exception that erroneously marks the socket as closed and sets it to non-blocking. Work-around code added to restore proper operation after such a timeout occurs.  (4301)
1.0.5.0    Released: 2007-06-08
  • Modified installation to improve Vista interoperability
1.0.4.0    Released: 2006-08-11
  • Telnet for .NET now supports 64 bit environments.
Product fixes in this release:
  • Telnet stops when it receives an option it does not know about  (3575)
1.0.3.0    Released: 2005-11-01
Product fixes in this release:
  • Corrected condition that would cause a "MemoryStream not expandable error" when using the Login method
1.0.2.0    Released: 2005-08-23
  • By popular demand, we have added an override for the Telnet.WaitFor method that takes an array of strings. This allows you to pass in multiple tokens. The method will return when any token is found. This is very useful when you are not sure what the exact response to a command will be. Also by popular demand, WaitFor no longer closes the connection when the token is not found. We have also addressed issues that prohibited usage in Visual Studio 2005 beta 2
Product fixes in this release:
  • Added an override for the Telnet.WaitFor method that takes an array of strings. This allows you to pass in multiple tokens. The method will return when any token is found. This is very useful when you are not sure what the exact response to a command will be
  • WaitFor no longer closes the connection when the token is not found
  • Addressed issues that prohibited usage in Visual Studio 2005 beta 2
1.0.1.0    Released: 2003-05-22
  • The latest version of PowerTCP Telnet for .NET enhances multi-threading support. Because use of multi-threading is expected to be far more common in .NET, and components will probably be used in conjunction with controls that exist on the primary User Interface (UI) thread, all the components included as part of this product now include a SynchronizeObject property. This property automatically controls thread marshalling between worker threads and the main UI thread. What this means is that if a component is returning from a BeginXXX method that triggers an EndXXX Event, setting SynchronizeObject to the parent form will allow code that exists in the EndXXX Event to properly use (marshall data) controls that exist on the parent form
Product fixes in this release:
  • Setting certain options in the Editor Form no longer prevents a project from being compiled
  • Added SynchronizeObject property to all components
  • Fixed a problem where the Telnet component would not properly close the connection in certain circumstances
  • Telnet.WindowSize is now a Size type