The installer is using a new tool but it should be backward compatible.

It should be a drop in replacement for the existing installers/merge modules but we have not tested every permutation of system.

If bugs exist they will be fixed.

using System;
using Opc;
using Opc.Da;

namespace OpcClientSimple
{
class Program
{
static void Main(string[] args)
{
// 1. Define the Server URL (Local or Remote)
// Format: opcda://[Hostname]/[ProgID]
string url = "opcda://localhost/Matrikon.OPC.Simulation.1";

Opc.IDiscovery discovery = new OpcCom.ServerEnumerator();
Opc.Server server = new Opc.Da.Server(new OpcCom.Factory(), null);

try
{
// 2. Connect to the Server
server.Url = new Opc.URL(url);
server.Connect();
Console.WriteLine("Connected to: " + server.Url);

// 3. Create a Group (Subscription)
SubscriptionState state = new SubscriptionState();
state.Name = "MyGroup";
state.Active = true;

Subscription subscription = (Subscription)server.CreateSubscription(state);

// 4. Add Items (Tags) to the Group
Item[] items = new Item[1];
items[0] = new Item(new ItemIdentifier("Random.Int4"));

items = subscription.AddItems(items);

// 5. Synchronous Read
ItemValueResult[] results = subscription.Read(subscription.Items);

foreach (ItemValueResult result in results)
{
Console.WriteLine($"Item: {result.ItemName} | Value: {result.Value} | Quality: {result.Quality}");
}

// 6. Cleanup
server.Disconnect();
}
catch (Exception ex)
{
Console.WriteLine("Error: " + ex.Message);
}
}
}
}..

If you change your OS you will need new drivers for whatever h/w you have no matter what API is provided.

If you have a h/w that is only supported on windows then you will have bigger issues than OPC compatibility.

If your h/w has a lower level API that does work on Linux then your best best is to write a UA server that uses this lower level API.

netstandard2.1;netstandard2.0;net46

https://opcfoundation.org/deve.....-packages/

If all of your OPC apps use later versions of .NET you should be able to safely delete opcrcw.* 

There is a need to update the OPC Foundation .net DLLs to remove the dependency on deprecated .NET versions that potentially increase the risk of vulnerability from a cyber security aspect.

These are the .dlls our Cyber team are finding delivered that are showing dependencies on deprecated .NET versions:

FileName Dependency (mscorlib/.net version)
opcnetapi.com.dll v2.0
opcnetapi.dll v2.0
opcnetapi.xml.dll v2.0
opcrcw.ae.dll v1.0.5000.0
opcrcw.batch.dll v1.0.5000.0
opcrcw.cmd.dll v1.0.5000.0
opcrcw.comn.dll v1.0.5000.0
opcrcw.da.dll v1.0.5000.0
opcrcw.dx.dll v1.0.5000.0
opcrcw.hda.dll v1.0.5000.0
opcrcw.sec.dll v1.0.5000.0

Historically, we have been using the JEasyOPC client on a Windows Server 2012 setup to retrieve switch information via the OPC DA protocol, with both the client and server running on the same machine. This configuration relied on DCOM, which is essential for OPC DA communication.
As part of our infrastructure modernization, we have migrated to a Linux-based environment. However, we are now facing a significant architectural challenge:

JEasyOPC is not supported on Linux, primarily due to its dependency on DCOM.
Our hardware supports only OPC DA, and not OPC UA, which limits our ability to adopt a fully modern OPC UA-based solution.

Given these constraints, we are exploring alternative architectures that would allow us to continue retrieving switch data while operating in a Linux environment.

Can you please suggest the Architecture on the OPC server and OPC client

Thanks.

I assumed that people still wanting to use the VB6 DLL would be running on very old system.

Since you want to integrate with powershell, which is a modern tool, you will need to use the .NET API which does support modern systems:
https://opcfoundation.org/deve.....urce-code/

There are old samples available to corporate members here:

https://opcfoundation.org/deve.....ls-classic

I'm new in OPC world and wanted to implement an application that exposes information that will be read by an OPC DA Client via DCOM.

The idea is that the values that are exposed in tags are values read from a database. That is, no data will be obtained from any external device.

My idea is to implement my application using C#, although if it were necessary to do it in another language, I could consider it.

As I have seen, I need the files opcda.dll, opcproxy.dll, opccomn.dll, opccomn_ps.dll and OpcEnum.exe to be able to do it.

I downloaded version 3.00.108 of OPC Core Components Redistributables from the OPC Foundation website, but it doesn't seem to include those files.

As I've been researching, I'd need version 2 of that package.

Could someone guide me on how to get that package or how to get the files I need?

Sorry if my question is very basic, but as I said before, I'm new in OPC world.

Thank you very much in advance.

https://opcfoundation.org/deve.....n-wrapper/

However, after installing the MSI (and extracting the ZIP version as well), I cannot locate opcautomation.dll anywhere on my system. I’ve checked the usual paths:

C:\Program Files (x86)\Common Files\OPC Foundation\
C:\Windows\SysWOW64\

I also searched the entire drive but the DLL doesn’t appear to be present.

Could someone confirm:

• Whether OPCAutomation.dll is still included in the latest redistributable?
• If not, is there a separate download or recommended source for obtaining it?
• Any steps I might have missed during installation?

Thanks in advance for your help!

0x4FFB0C0 looks like random memory.