A: Not usually. Agents normally use the “well-known” port 161 for communications. Since Microsoft’s Agent would be using this port, your application would have to use a non-standard port, and your managers would have to be configured to check your non-standards port (which can be done is some cases, but not commonly).
Back to Top

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

A: Yes to all of the above. PowerTCP uses SnmpTable and SnmpTableRow objects to easily traverse tables, and version 2 commands (such as GetBulk) are fully supported.
Back to Top

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. Also, we provide integrated Editor Forms which can be used for protocol testing.
Back to Top

A: Suppose a PC host is being used to control a hardware device. You could create an agent that, when queried, would respond with statistics from your hardware device. This concept could be extended to provide any kind of information that is collected and made available by the host (using SNMP standards).
Back to Top

A: A typical application would store the IP address of all the agents on the network, and would gather statistics from the agents on a schedule. The application’s address might also be registered with the agents for trap purposes, so the manager would be asynchronously (dynamically) informed of significant agent events. Information would be logged to a file and dynamically displayed through the user interface.
Back to Top

A: Portability to other (future) .NET environments is one of the biggest benefits. Products using native .NET classes will generate Intermediate Language (IL) code that will run under UNIX or LINUX once those run-time environments are developed. In addition, your will find that 100% managed code will demonstrate fewer maintenance issues in the future. There is simply less to go wrong when programming mistakes are made. Did I just say that programmers and QA programs aren’t perfect? Oops.
Back to Top

A: There appears to be a problem with Delphi 8 Web applications and the way its handling the .NET licences.licx file that stores the list of licensed 3rd party components. Below you will find the steps to duplicate this problem and correct it:

Steps to recreate problem:

• 1) Download a trial version of PowerWEB TextBox for ASP.NET 
• 2) Run the setup and make sure that "Create IIS Virtual Directories" is checked
• 3) Make a new ASP.NET project called BorlandTB
• 4) Insert a Dart.PowerWeb.TextBox.HtmlBox control onto WebForm1
• 5) Line 17 of BorlandTB.bdsproj will contain an incorrect reference to the compiled license dll. If you manually set this to: {$R 'bin\BorlandTB.dll.licenses' 'licenses.licx'} It will work

Back to Top

A: The initial release of Delphi 8 did not properly support 3rd party component licensing in ASP.NET. Please download the latest update from Borland that will address this issue.
Back to Top

A: When used without SSL encryption, there is no problem navigating firewalls or proxies. If you are using SSL encryption, only SOCKS proxies will properly allow navigation in secure mode.
Back to Top

A: No. PowerTCP directly encodes/decodes messages and sends/receives them using standard system services (Winsock API).
Back to Top

A: When developing a client application, our customers will typically start using our product synchronously because it is easiest to implement. Later, the application may be changed to use asynchronous communications as the application is optimized. Eventually, the application may even be ported to ASP, where synchronous operation is required. Our customers like the flexibility we provide with these two models incorporated into the same product.
Back to Top

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