Version: 4.9.4.0
Create custom SNMP Manager, Trap and Agent applications for monitoring and controlling network devices. 
Q: How is PowerSNMP for .NET different than other SNMP products?
A:

This latest version of the venerable PowerSNMP 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:

  • SNMP version 1, 2 and 3 with authentication, encryption/decryption
  • Built-in objects, identifiers, traps, tables, notifications, and groups as defined in RFCs 1155, 1157, 1158, 1213, 2578, 2579, 3417 and 3418
  • MIB parsing, where any custom MIB file can be used to generate C# or VB classes in source code
  • MIB compiling, where any custom MIB file can be used to generate dynamic classes and objects at run-time
  • Start method for easily implemented mult-threaded applications, including cross-threading marshaling support
  • EncodedMessage property for easy debugging of bytes sent and received, as well as session logging

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, PowerSNMP for .NET 4.x was designed with the following emphases:

  • Improved Asynchronous Support
    Traditional PowerSNMP 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
    PowerSNMP 4.x has taken advantage of generics and other features introduced in .NET 2.0.  Now that most users have migrated from .NET 1.x, PowerSNMP 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.

  • 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 PowerSNMP fully support getting values from a table? How about GetBulk?
A: Yes to all of the above. PowerSNMP includes high-level table retrieval methods, and version 2 commands (such as GetBulk) are fully supported.
Back to Top
Q: How could an application use the Manager control?
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
Q: How could an application use the Agent control?
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
Q: Can I create an Agent that works as a sub-agent to Microsoft’s OS Agent?
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-standard port (which can be done is some cases, but not commonly).
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