Log In
Home
05/12/2015
Offline
The installer was build with the now discontinued VS installer project support in VS2008 and likely has issues with newer OSes. It needs to be rebuilt with a newer framework.
05/12/2015
Offline
The DLLs can now be downloaded in a signed ZIP from the OPC Foundation website:
05/30/2017
Offline
We have a updated versions of the Merge Modules ad MSI which now have sha256 signatures.
Please contact me if anyone is able assist with beta testing the new binaries.
09/11/2015
Offline
Thank you very much.
Now that the .dll files (OpcNetApi.Com.dll, OpcNetApi.dll and OpcNetApi.Xml.dll) are available, is there any place, document or web page on which the classes and methods that compose these .dll are documented?.
When somebody wants to start programming, this type of documentation is essential to know the possibilities of the dll's.
Thank you in advance.
05/30/2017
Offline
The 107 MSM/MSI (not posted yet) will install the .NET documentation files for the assemblies.
09/02/2014
Offline
The RCWs are now part of the "OPC .NET API 4.5 Redistributables.msi" file. But I can't find the RCW Merge Module published (or am I looking in the wrong place?). The "OPC .NET 4.5 RCWs MergeModule.msm" is found in the source build zip package, but it is not signed. Could you please also publish a signed RCW Merge Module?
05/30/2017
Offline
Working on nuget packages for the RCWs.
This should get rid of the installers and make life easier for everyone.
09/02/2014
Offline
Please also supply signed Merge Modules of RCWs. We still need signed installers or Merge Modules.
05/30/2017
Offline
Johan Heikkila said
Please also supply signed Merge Modules of RCWs. We still need signed installers or Merge Modules.
Why would you need this? When you make your own installers you can distribute a copy of the RCWs in your application directory.
The nuget packages facilitate this.
The COM ProxyStubs will still have installers.
05/30/2017
Offline
Release 107 is now posted as a release candidate:
The 107 release has a number of significant improvements:
• All binaries are signed with SHA256. For backwards compatibility the binaries also have a SHA1 signature, however, SHA256 is now required to pass Windows Authenticode verification.
• The dependencies on .NET Framework have been removed from the Core Components Installers and Merge Modules. The x64 Installer always installs the x86 version so only one version of the MSI is required for any system (both can still be installed but it is redundant).
• The .NET RCW and .NET API assemblies are now distributed as nuget packages which support .NET 3.5/2.0 and .NET 4.0. The sample client code illustrates how to use these packages. The Core Components Installers no longer install the assemblies the GAC.
• The Core Components Merge Modules now use the MSI Component IDs that match the 105 release. This should prevent necessary components from being uninstalled when an application that uses the Merge Modules is uninstalled. This problem will still exist if a product uses the 106 release, however, there should be a smaller number of those products. Version 106 has been removed from the website because of the inconsistent Component IDs.
See:
https://opcfoundation.org/deve.....omponents/
https://opcfoundation.org/deve.....e-clients/
https://opcfoundation.org/deve.....e-servers/
05/15/2015
Offline
i downloaded a sample project from mesta automation
when i ran the project in Visual studio 2017 with .NET 4.6 i get the following error
System.IO.FileNotFoundException: 'Could not load file or assembly 'OpcRcw.Dx, Version=1.0.1.21, Culture=neutral, PublicKeyToken=9a40e993cbface53' or one of its dependencies. The system cannot find the file specified.'
i downloaded the OpcRcw.DX and included in the project and tried again but this error still there.
i'm running VS on a Win7 64 bit PC.
anyone can help me ?
05/30/2017
Offline
The projects are using an old version of the RCWs (x86 and .NET 1.1 ONLY).
You need to upgrade to use OpcComRcw 2.01.107.
This will require that you remove the old references and add a reference to the new NuGet packages which are installed with CoreComponents when the 'install headers' option is checked.
1 Guest(s)
Usage Policy