IOP: BrowseNext continuation is not always handled correctly, when multiple nodes are browsed

[mregen]

Type of issue

• Bug
• Enhancement
• Compliance
• Question
• Help wanted

Current Behavior

The browse continuation must take into account that a server may have only a limited number of continuations. BrowseNext must be called first before issueing the next browse, specifically if the call is batched in multiple service calls, and for the status result: BadNoContinuationPoints the browse must be repeated.
The ClientSample handles the browse correctly, but e.g. NodeCache internally does not.

Expected Behavior

No response

Steps To Reproduce

Browse a server with many nested nodes that contain a lot of child nodes which cause a continuation with BrowseNext.
Browse results may be incorrect if the BadNoContinuationPoints is ignored or if a new Browse is started before the continuation points are processed with BrowseNext.

Environment

- OS:
- Environment:
- Runtime:
- Nuget Version:
- Component:
- Server:
- Client:

Anything else?

No response