Simple

This is a simple server with a few items, statically defined within the code.
A simulation thread increments the item values and updates the server cache.
Write calls write the item value into the simulation buffer, forcing the incrementing to continue from the written value.

Properties

This sample works as the 'Simple' sample and additionally defines an handles custom item properties.

Dynamic

This sample is very similar to the 'Properties' sample but implements a dynamic item address space.
At startup no items are defined in the generic server. All items are added dynamically when they are first accessed by a client. The browse mode is set to virtual and the client browse calls are handled in this sample. The return the items that could be added to the server cache.
For the client this handling is invisible. It appears identical to the 'Properties' sample.
The XDARap Professional Edition is required because the Standard Edition does not support virtual browsing.

ConfigBuilder

This sample loads the item configuration from the file CfgSample.xml and creates the defined items at startup.
The XML file can be modified with the ConfigBuilder application. The new configuration used when the server is restarted. No compilation is required.
The sample does embed the XML file to show this possibility. To use the embedded file the sample has to be modified to use the LoadEmbedded() method in place of LoadFromExeDir(). The method call is in the code as comment.

20kItem

This sample defines 20000 items at startup and updates the first 1000 items every 100ms.
It should give an impression of the performance and can be used as the base for a custom benchmark application.
On a 2GHz Pentium the startup takes about 2 seconds and the CPU load is around 6%.

TCPDevice

This sample uses a TCP socket on port 6500 for device communication. For tests a Device simulator console application is provided.
The IP address is initialized as localhost, allowing both applications to run on the same computer.
At startup the DeviceSimulator sends a line with item names and the server creates these items in it's address space. The DeviceSimulator then periodically increments the item values and sends lines with the values of all items. The server customization reads these lines and updates the server cache. Items written by a client are sent to the DeviceSimulator, which displays them.

StockQuotes

This sample application shows how a server can be implemented to handle a huge number of items.
The server uses the dynamic address space mode and creates items when they are first accessed.
The current stock quotes are read from the Internet, showing a sample how an OPC server can access the Internet.
The client accesses the server with a stock symbol as the item name. The server then tries to read the current quote for this symbol and if successful adds the item to it's address space. The item value is then periodically updated.

WCF Remoting

The server plug-in assembly uses a WCF connection to communicate with another .NET application. Using the NamedPipe binding such a connection is highly efficient.

Self-Hosted

This sample shows how a .NET3 (WCF) XML DA server can be hosted in a Windows Forms application.