Online Forums
Technical support is provided through Support Forums below. Anybody can view them; you need to Register/Login to our site (see links in upper right corner) in order to Post questions. You do not have to be a licensed user of our product.
Please read Rules for forum posts before reporting your issue or asking a question. OPC Labs team is actively monitoring the forums, and replies as soon as possible. Various technical information can also be found in our Knowledge Base. For your convenience, we have also assembled a Frequently Asked Questions page.
Do not use the Contact page for technical issues.
- Forum
- Discussions
- QuickOPC-Classic in .NET
- Installation, Deployment
- Publickey of DLLs when using disabled prerequisites boxing
Publickey of DLLs when using disabled prerequisites boxing
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
github.com/AlinMoldovean/UA-.NET/commit/29208043d338c967537615419367f81b48d78231
Please Log in or Create an account to join the conversation.
There seem to be at least two changes made to address github.com/OPCFoundation/UA-.NET-Legacy/issues/1 .
The first is github.com/OPCFoundation/UA-.NET-Legacy/commit/552f5c2d8eed8df3eb34d1d00edafa82884e2707 . We already have this one in QuickOPC, because we are using the 1.03.342 release.
The second is github.com/AlinMoldovean/UA-.NET/commit/29208043d338c967537615419367f81b48d78231 .We do not have this second one in QuickOPC currently (it is not part of any release on GitHub yet).
Are you saying that to fix your problem, you need the second one too?
Regards
Please Log in or Create an account to join the conversation.
Nobody has a support contract with us, we do not offer that. We have "upgrade assurance", which allow cost-effective access to newly released versions, but that is unrelated to support. The way we do support is that we support everybody to maximum reasonable/viable extent, but we provide no guaranteed support.
If you do not have upgrade assurance covering the date of us releasing the new version, you will need to purchase a version upgrade in order to use it.
Regards
Please Log in or Create an account to join the conversation.
Our core problem are exceptions coming from your OPC stack, just as described here:
www.opclabs.com/forum/ua-general/2444-opc-ua-bindings-tcpasy...timeout-system-object?start=10
These exceptions happen multiple times per day. Our software is running at a major automotive company in Germany and we have to improve the situation as soon as possible. Our applications terminates several times per day.
This error has already been fixed at OPC foundation (see github.com/OPCFoundation/UA-.NET-Legacy/issues/1), but your SDK does not include this fix since was OPC foundation did not release it.
We would prefer to get a updated version of QuickOPC, which includes this fix.
We are aware that we do not have an active support contract. Any suggestions to solve these problem (technical and commercial) are welcome.
We can have a personal telephone call (or Skype) if this helps to solve the problem.
Kind regards
Peter
Please Log in or Create an account to join the conversation.
You have purchased a product of ours, which includes some 3rd party libraries. This is also the case of certain OPC Foundation libraries you are referring to.
We are signing them with our key (they came unsigned by OPC Foundation), because strong-named assemblies (which is a requirement by many customers) of QuickOPC can only reference strong-named assemblies as well.
As a side note, of course we would not be willing to provide any support if what you are using was not what we have assembled as a product.
If there is a need to change something, it'll have to be done by us.
Very importantly though, there are also various licensing restrictions. It is complicated, but here are some (simplified) that you need to be aware of (in my understanding, IANAL):
- If we, as OPC Foundation Members, make a change to the code of those libraries, we need to provide that change back to OPC Foundation (RCL license). That would not be technically impossible, but we have a policy that we do not make such changes if at all avoidable.
- You (I suppose you are not an OPC Foundation Members) cannot use the UA stack source code that you get from OPC Foundation in your product without making source code of your product, and any modified libraries, public (GPL). See opcfoundation.org/license-agreement/ .
Regards
Please Log in or Create an account to join the conversation.
We have to apply a patch to this DLL, how can we do that?
Kind regards
Peter
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
- Forum
- Discussions
- QuickOPC-Classic in .NET
- Installation, Deployment
- Publickey of DLLs when using disabled prerequisites boxing