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.
Property with a different name in the new release
07 Jan 2019 17:48 #6952
by support
Replied by support on topic Property with a different name in the new release
Hello.
I understand the issue, and your concern. We have not done this on our own,. however, and cannot easily prevent it from happening. Microsoft did it for us
Put shortly, when the COM type library is generated from the QuickOPC .NET classes, Microsoft's TBLEXP tool mixes up the casing when there are multiple occurrences of the same name (anywhere in the library) with different casing. For example, we might have a parameter called 'password' *somewhere else*, in an unrelated part of the product. And TLBEXP sometimes -randomly - chooses to rename the method or property called Password to 'password'.
More info:
Best regards
I understand the issue, and your concern. We have not done this on our own,. however, and cannot easily prevent it from happening. Microsoft did it for us
Put shortly, when the COM type library is generated from the QuickOPC .NET classes, Microsoft's TBLEXP tool mixes up the casing when there are multiple occurrences of the same name (anywhere in the library) with different casing. For example, we might have a parameter called 'password' *somewhere else*, in an unrelated part of the product. And TLBEXP sometimes -randomly - chooses to rename the method or property called Password to 'password'.More info:
Best regards
Please Log in or Create an account to join the conversation.
07 Jan 2019 17:11 - 07 Jan 2019 17:12 #6951
by federica
Property with a different name in the new release was created by federica
Hi,
I'm using your SDK (QuickOPC 2018.1, in particular OPC-UA under COM with C++) since last year.
Now I'm testing the new version QuickOPC 2018.3 and I noticed you changed the name of a property (from "Password" to "password").
In particular,
With QuickOPC 2018.1:
_UASmartSessionParametersPtr SessionParms = IsolatedParameters->GetSessionParameters();
SessionParms->UserIdentity->UserNameTokenInfo->Password = pwdParam;
With QuickOPC 2018.3:
_UASmartSessionParametersPtr SessionParms = IsolatedParameters->GetSessionParameters();
SessionParms->UserIdentity->UserNameTokenInfo->password = pwdParam;
Why did you do that?
Is it a mistake?
Will you restore the old property name with the new release?
It gives me some concern with the distribution of my applications....
Thank you!
I'm using your SDK (QuickOPC 2018.1, in particular OPC-UA under COM with C++) since last year.
Now I'm testing the new version QuickOPC 2018.3 and I noticed you changed the name of a property (from "Password" to "password").
In particular,
With QuickOPC 2018.1:
_UASmartSessionParametersPtr SessionParms = IsolatedParameters->GetSessionParameters();
SessionParms->UserIdentity->UserNameTokenInfo->Password = pwdParam;
With QuickOPC 2018.3:
_UASmartSessionParametersPtr SessionParms = IsolatedParameters->GetSessionParameters();
SessionParms->UserIdentity->UserNameTokenInfo->password = pwdParam;
Why did you do that?
Is it a mistake?
Will you restore the old property name with the new release?
It gives me some concern with the distribution of my applications....
Thank you!
Please Log in or Create an account to join the conversation.
Moderators: support
Time to create page: 0.060 seconds