Hi Team,
Today, I have updated my SDK from V3.4.1 to V4.1.0 and found that my current code breaks.
protected override RequestContext ValidateRequest(RequestHeader requestHeader, IEndpointIncomingRequest incoming,
ServiceType requestType)
This over loaded method from ServerManager.cs is throwing an error and I found that in the new version the method signature changed as
protected virtual void ValidateRequest(RequestHeader requestHeader)
Three parameter changed to one parameter and method return type change from "RequestContext" to "void"
Am I missing something?
Please help
Regards,
Harshal
Method signature mismatch between V3.4.1 and V4.1.0 ??
Moderator: uasdknet
-
- Sr. Member
- Posts: 12
- Joined: 13 Dec 2023, 21:31
- Support Team
- Hero Member
- Posts: 3190
- Joined: 18 Mar 2011, 15:09
Re: Method signature mismatch between V3.4.1 and V4.1.0 ??
Hi,
We refactored the method when releasing SDK version 4.0. We renamed the method to CreateRequestContext and added the argument 'channelContext'. However, since we did not see use cases to override this method by the application, we did not mention this in the migration guide.
Check out documentation here and change your code accordingly to migrate to v4.1.0:
https://documentation.unified-automation.com/uasdknet/4.1.0/html/classUnifiedAutomation_1_1UaServer_1_1ServerManager.html#af5eca9fd8c108fea989778efaf623fc1
We refactored the method when releasing SDK version 4.0. We renamed the method to CreateRequestContext and added the argument 'channelContext'. However, since we did not see use cases to override this method by the application, we did not mention this in the migration guide.
Check out documentation here and change your code accordingly to migrate to v4.1.0:
https://documentation.unified-automation.com/uasdknet/4.1.0/html/classUnifiedAutomation_1_1UaServer_1_1ServerManager.html#af5eca9fd8c108fea989778efaf623fc1
Best regards
Unified Automation Support Team
Unified Automation Support Team