The Distinct ONC RPC/XDR Toolkit for .NET is a set of tools and libraries that enables you to write pure .NET ONC RPC clients and servers. It can be used with C#, C++/CLI or Visual Basic.NET (VB.NET). This is the only ONC RPC for .NET currently available.
This Toolkit may be used to help you out in several different scenarios. Here are some:
- Whenever you wish to write an ONC RPC client in any .NET-language to communicate with existing ONC RPC/XDR servers.
- Whenever you wish to preserve the existing interface of an application written using the XDR specifications.
- Whenever you wish to write C# code that can read and write XDR streams. Other (for example C, C++ ) applications often use this platform independent encoding format for serializing data.
- Whenever you wish to write simple client/server applications in .NET.
In all these scenarios Distinct ONC RPC/XDR for .NET will certainly help you to write portable, high-quality C# code in a minimum amount of time that can be used from any .NET-language.
System Requirements
This Toolkit requires the 32 or 64 bit versions of Windows XP, Windows Vista, 2003 Server or 2008 Server. Note that for XP and 2003 Server .NET service pack 1 is required.
This product will not work in the .NET framework 1.1. If you need to support a legacy system that does not have the .NET framework 2.0 or higher please contact Distinct Sales for a possible solution.
What comes with the RPC for .NET ?
The Distinct ONC RPC / XDR for .NET Toolkit consists of:
- The Distinct ONC RPC/XDR for .NET assembly that contains the ONC RPC/XDR run time libraries that conform to RFC 1831 (RPC: Remote Procedure Call Protocol Specification Version 2) and RFC 1832 (XDR: External Data Representation Standard). The API consists of classes that allow you to write .NET clients, for standard RPC servers that can be embedded in applets and be run by a standard Web browser. It also allows you to develop ONC RPC stand-alone servers. The package allows connections over TCP and UDP.
- An RPCBIND application that implements the RPCBIND protocol versions 2 (portmapper), 3 and 4.
- The Rpcgen.NET compiler that translates standard RPC/XDR interface definition files into C# classes that implement the client-and server side stubs and the XDR conversion routines for the described interface. This means Rpcgen.NET implements a C# language mapping for .x IDL files.
- The RPCInfo utility displays a list of all the services registered with the RPCBIND on a system. This utility can be used to query the RPCBIND on the local host (by specifying "localhost" or no host name at all on the command line) or on a remote host (by specifying the name of the host as a command line argument). Source code for the RPCInfo utility is included for reference.
- A set of demo applications that consist of an XDR file which describes an interface of a very simple server, the server implementation, and demo applications that invokes the server written in both Visual Basic.NET and C#.
Unique Features:
- New Flexible Port Range Feature for servers.
It is now possible for the administrator to define a range of ports that a server will register on. This means that if you need to use a Distinct RPC.NET Server through a firewall, you can now restrict the number of ports that need to be opened on your firewall to those specified.
- Support for 32 and 64 bit Windows platforms and both IPv4 and IPv6 in a single toolkit.
Expected time savings: 48 man-months
Expected time savings is the time that, based on our experience, would take a skilled developer with good understanding of TCP/IP networking and very well versed in C or C++, to develop this object. This time can be used as a guideline of the cost involved if you choose to develop it yourself or have someone else develop it for you.
Technical support.
We stand behind our product 100%.
Check out our new support center. You will find the most comprehensive technical support center in the net tools business, featuring a comprehensive knowledge base, AskCody™ and an email-based Support Center.
Additional RPC resources
The Distinct ONC RPC Toolkits comply with the standard specifications found in the public documents known as RFCs) (Request For Comments). To access these RFCs, clink on the links below:
RFC 1831 (RPC: Remote Procedure Call Protocol Specification)
RFC 1832 (XDR: External Data Representation Standard).
RFC 1833 (RPC: Binding Protocols)
Recommended Book
We recommend reading "Power Programming with RPC." The author is John Bloomer and the publisher is O'Reilly & Associates, Inc. This book explains how to use remote procedure calls to distribute applications to multiple heterogeneous computers or servers on your network.
Product Documentation for RPC / XDR for .NET version
View product guide for RPC / XDR for .NET.
Trial Download:
RPC / XDR Toolkit for .NET
|
