Most OPCDA.NET components are only used during the application development.
Only the referenced edition of the OPCDA.NET DLLs ( e.g. the file OpcDaNet.Net4.dll or OpcDaNetWpf.Net4.dll and OpcNetBase.Net4.dll ) are required at run-time.
The OPCDA.NET DLLs are copied into the application folder by Visual Studio when the OPCDA.NET reference is added and are copied to the application output folder when the application is compiled. The OPCDA.NET DLLs need to be deployed with the other application components.
Test Clients
The test clients may optionally be deployed with the application if it could be necessary to test the server access in case of difficulties due to e.g. security permission settings.
The test clients are in the folder TOOLS in the OPCDA.NET product installation directory.
| OPC V2 test client: | OPCDATestClientNet4.exe OPCDATestClientNet4X86.exe |
built for .NET 4, ANY CPU built for .NET 4, X86 platform (always runs in 32bit mode) |
| OPC V3 test client: | DA3TestClientNet4.exe DA3TestClientNet4.options.xml |
built for .NET 4, ANY CPU |
Simulation Server
The OPC DA V2/V3 simulation server DAESimServer.exe may optionally be deployed with the application if it could be necessary to test the server access in case of difficulties due to e.g. security permission settings. It is in the folder TOOLS in the OPCDA.NET product installation directory.
OPC Core Components
If the application is deployed to a computer without an installed OPC server then it may be necessary to install the OPC Core Components.
The OPC Core Components V 3.0.106 are provided in a 32bit and a 64bit version:
- OPC Core Components Redistributable (x86).msi
- OPC Core Components Redistributable (x64).msi
On 64bit systems the components install a new component called the Category Manager. This component makes x64 servers visible to x86 clients.
The x64 version of the Core Components Redistributables installs the 32bit versions so it is the only package that needs to be installed on x64 systems.
All .NET assemblies are placed in GAC.
Security Permission settings
Security Permission settings are the most likely cause for difficulties. If the application is deployed to an Windows XP SP2 system then the system has to be configured according the instructions in the document Using OPC via DCOM with XP SP2.pdf supplied in the folder OPC in the OPCDA.NET product installation directory.
Be aware that for callbacks from the server the roles of DCOM server/client are exchanged and the client application acts as the COM server for the callbacks. OPCDA.NET creates registry entries to allow everybody the right for callbacks. However in order to be able to do that the application needs the permission to write the registry key HKEY_Classes_Root\AppId
You may use the registry editor RegEdit to check if a key with the name of exe file was created.