Log In
Home
11/23/2014
Offline
The published OpcNetApi (Nuget packages in https://opcfoundation.org/deve.....omponents/ zip-file) are targeted for .Net 2.0 and .Net 4.0 only.
Even if classic OPC is considered as legacy by many, there are still many suppliers that only supports classic COM servers (in-proccess and out-of-process) and it would be superb if the OpcNetApi could be targeted for .Net Core.
(and later .Net 5 after end of next year when there is no Cre and Full framework anymore, only .Net 5 and up (which are basically evolutions of .Net Core 3).
One of the showstoppers when trying to refer to OpcNetApi from a .Net Core 3 app is that some types (e.g. FILETIME) used in the API resides in the System.Runtime.InteropServices instead of System.Runtime.InteropServices.ComTypes even when the first is considered obsolete and the latter is defined in all frameworks except 1.0.
I don't know about other types which are stoppers, but probably quite a few structs, interfaces and enums, but I guess this is not to much work if the source code could be made available (github?) or the job just to be done and published at opcfoundation.org site.
Any views, comments etc.?
05/30/2017
Offline
OPC Foundation Corporate Members have access to all of the source code.
11/23/2014
Offline
Thanks, however that would simply be too high a price for our small company's tiny, but still necessary use of classic OPC.
Is there any plans of publishing such .Net Core 3 port of Core Components accessible for registered users?
05/30/2017
Offline
It is tentatively scheduled for Q4 2019. That date could slip if more immediate issues come up.
11/23/2014
Offline
Than
Randy Armstrong said
It is tentatively scheduled for Q4 2019. That date could slip if more immediate issues come up.
Thanks a lot, that sounds very good
11/23/2014
Offline
Randy Armstrong said
It is tentatively scheduled for Q4 2019. That date could slip if more immediate issues come up.
Any news about the matter?
05/30/2017
Offline
Started some initial work. Looks like it is not a simple process.
11/23/2014
Offline
Would open sourcing it be a good idea?
05/30/2017
Offline
The OPC UA codebase is all open source because that is the codebase that OPC-F would like people to use.
11/23/2014
Offline
Sure, but I think there is still plenty lecacy classic servers out there and .net core is what MS like developers to use...
11/22/2019
Offline
Thanks, however that would simply be too high a price for our small company's tiny, but still necessary use of classic OPC.
Is there any plans of publishing such .Net Core 3 port of Core Components accessible for registered users?
05/30/2017
Offline
The .NET Standard RCWs are here:
05/30/2017
Offline
I have the .NET API client code built with .NET Core and talking to a DA server.
I could use assistance beta testing.
Please email randy.armstrong opcfoundation org if you can help.
11/23/2014
Offline
Randy Armstrong said
I have the .NET API client code built with .NET Core and talking to a DA server.I could use assistance beta testing.
Please email randy.armstrong opcfoundation org if you can help.
I sent you an e mail about a week ago, have you seen it?
05/30/2017
Offline
This issue should be fixed in the 108 that was posted today.
It will be RC until Jan 15th to give people a chance to test and report issues.
04/24/2020
Offline
EuroEager2008 said
Would open sourcing it be a good idea?
I like this idea. Can we please make the OPC Classic open source? I am actually hoping to work on COM/DCOM server in my free time. Making the reference code in Github would be perfect.
Let us (me) know how we can help to make it open source.
09/05/2019
Offline
Hi everyone
I need some help. I installed the opc-core-components-redistributables-3.00.108-20191220 downloaded from the OPC Foundation. Does not give an error but the DLLs (OpcComRcw.) do not appear in C: \ Windows \ assembly
Can you help me?
Thanks in advance
05/30/2017
Offline
The RCW is no longer installed with the CoreComponents.
Users need to use a NuGet package that was available to members only.
This was an oversight that has been corrected. The NuGet is available to all registered users:
09/05/2019
Offline
Randy Armstrong said
The RCW is no longer installed with the CoreComponents.Users need to use a NuGet package that was available to members only.
This was an oversight that has been corrected. The NuGet is available to all registered users:
https://opcfoundation.org/deve.....omponents/
Thank you and take care
02/29/2024
Offline
I agree about the open sourcing. Lots of us are still stuck with using classic OPC and have to deal with the ever-changing environments. Paywalling the apis and the source does not help and just makes me want to abandon OPC altogether.
2 Guest(s)
Usage Policy