Add secure Telnet, rsh, rexec and rlogin connectivity to any .NET application or service.
Q: How are PowerTCP Emulation for .NET and Telnet for .NET different from other Telnet products?
A: The latest versions of PowerTCP Emulation for .NET and Telnet for .NET get 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 mult-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

The .NET environment has evolved, and so has its users. Customers are developing more applications for ASP.NET, more console applications, and more service applications. Lacking UIs, pseudo-blocking and asynchronous methods are not relevant for these environments. There are also trends towards greater levels of customer control. For these reasons, Telnet for .NET 4.x was designed with the following emphases:

  • Improved Asynchronous Support
    Traditional PowerTCP asynchronous support provided a means for executing methods on worker threads, but this required a signaling mechanism indicating when operations completed. This resulted in difficult-to-maintain, event-driven code. With the new design, code is more self-documenting, uses fewer resources, and is more flexible to use.

  • Improved Re-Use of .NET 2.0 Features
    PowerTCP 4.x has taken advantage of generics, improved support for X509 certificates, and other features introduced in .NET 2.0.  Now that most users have migrated from .NET 1.x, PowerTCP can be upgraded without sacrificing backward compatibility. Of course, the .NET 1.x product line will still be licensed for use in the .NET 1.x environment to support legacy applications.

  • Integrated Security
    Secure Socket Layer (SSL) security is integrated into the core product, so that SSL encryption is included in each new product.

  • Support for .NET CF (Compact Framework)
    Comprehensive support of the Compact Framework has been extended with the new design.

Back to Top
Q: How does the trial version differ from the licensed version?
A: There is no difference between a non-licensed "trial" version of the product and a licensed version during development.

At runtime, an application built without a valid Developer License will periodically show a trial message.  Other than this message, there is no difference in functionality.

Back to Top
Q: Do samples ship with the product?
A: Absolutely. We ship complete finished apps (not just simple technology demonstrations) in both CSharp and Visual Basic .NET as both Windows Applications and Web Applications.
Back to Top
Q: Does your product support streaming operation?
A: Yes. This product is architected on the basis of streams and almost anything can be represented as a stream.
Back to Top
Q: Extensive designer support? What does this mean?
A: We provide extensive support to help you design, develop, and debug quicker and easier than ever before. For example, we provide full Help 2.0 documentation (including tutorials) which integrates directly into Visual Studio .NET.
Back to Top
Q: Why do I see an 'Attempting to deserialize an empty stream' exception when I build my VS.NET 2008 Website?
A: Websites create an App_Licenses.dll for component licensing which must be distributed with the application.  Due to an apparent VS.NET 2008 bug, this dll is faulty when created during compilation on a 64 bit Operating System.  To work-around the problem, the App_Licenses dll in the 2008 Website can be replaced. 

Options include:
a) Compile a 2005 WebSite on the same (licensed) machine using the same controls/components
b) Compile a 2005 or 2008 WebSite on a 32 bit OS machine, provided this machine is also licensed (Dart Developer licenses allow installation on up to two machines)

Replace the faulty App_Licenses.dll with the resulting dll from one of the options above, and the Website should build and deploy without issue.  Do not delete the new dll, or VS.NET will again create a new faulty one in its place.

Back to Top
Q: Why do I get a license exception when creating C++ CLR projects in VS2010 and VS2012?
A: Visual Studio 2010 and Visual Studio 2012 do not automatically embed the license for licensed components into the compiled binary. Because of this, you will receive a LicenseException at run time. To resolve the problem please follow these steps:
  1. Right-click on the project in the Solution Explorer and select Build Customizations from the context menu.
  2. In the Available Build Customization Files pane, check the lc(.targets, .props) checkbox. Click OK.
  3. Right-click on licenses.licx in the Solution Explorer, and select Properties from the context menu.
  4. In the Property Pages, select General in the Configuration pane, then select License Compiler in the Item Type drop-down. Click OK.

Back to Top