06/17/2014
How to develop a OPC-UA server to also run on Windows XP Embedded (.NET 4.0)? We are thinking about this, because a lot of our PLCs are running on existing industrial pc’s.
Is it possible to target the actual core components to .net 4.0 and develop a first version of our OPC-UA server?
Which base would you recommend to start? (older version, other SDK)
05/12/2015
SDK vendors like Unified Automation support .NET 3.5 with their .NET SDK.
If you want to use the OPC-F codebase you can go back to older versions but this will mean you will lose new features and bug fixes (support for new security policies will be the most serious issue). You should be able to re-target the code base and remove code that does not compile.
06/17/2014
Okay, thank you for the recommendation.
For future use we want to work with the OPC-Foundation codebase.
Starting with an example from the current version of UA-.NET (1.03.342). Using the “Reference Server” from the “Sample Applications” folder. Retarget the project and all of it’s dependencies to .NET 4.0:
– So far it is building and running without any modification of code. I understand that this is an “untested” situation.
10/02/2014
You can target the .net 4.0 network with .Net 3.5 libraries. The following KB article form KEPware explains how to do this for the ClientAce v3.5 version. Those libraries targeted .Net 3.5.
https://www.kepware.com/suppor…..000000S6XD
This information came from an MSDN KB article. You also have to make sure the embedded XP image has been updated to support .Net 4.0 as that was not originally supported.
1 Guest(s)