UA-.NETStandard | OPC Unified Architecture .NET Standard | DevOps library

I wanted to learn some C# and .net and network stuff. Thus, I've chosen the OPC UA code.

On github: UA-.NETStandard/Stack/Opc.Ua.Core/Stack/Client/DiscoveryClient.cs

But I really don't understand how this method works:

I'm fairly new to OPCUA and could use an example on how to implement the AddNodes service in C# using the official .NET Standard SDK. Basically what I want to do is implementing my custom server and be able to call the AddNodes service from the client to add some nodes to a folder (and set their initial values).

I have seen there are various classes to inherit from, so I thought it would be the best to inherit from StandardServer and override the AddNodes method. After that, I could create my own custom node manager and call it from within this method. However, none of the sample node managers implement an AddNodes method (even the INodeManager interface doesn't) so I'm wondering if I am on the right track.

Has somebody already implemented the AddNodes service using this SDK and is willing to give me some hints how to do so? Did you just create your own AddNodes method on your custom node manager and add the nodes there? Some code snippets would be very helpful. Thank you!

Reading through some of the OPC UA documentation that is out there (OPC UA eBook), (github repo), (Home page) you come across Type definitions and how they can be used to blueprint any object that references it.

However, going through some of the example code in the github repo, I can't find a clear example how a type definition makes data access easier or cleaner.

For instance: In solution 'UA QuickStart applications' in the github repo there is windows forms project 'Boiler client' that uses 2 different 'Boiler Type' instances in the address space and projects its variables onto textboxes depending of the selected combobox item.
When looking at the code you can see that the boilers are indeed selected using the 'Boiler Type' flag but the properties that are to be mapped are still hardcoded and found using relative paths instead of using the Type.

Two different boiler instances

Fetch boilers method

Boiler client with seperate variable display

Currently, consuming OPC UA data( nodes) for me means I have to make a list of each and every one of all the node addresses I want to read and using them in the Session.Read() or listening on them with a MonitoredItem.
Instead, I think it should be possible to read all the nodes in an object and map them to CLR object.

My Question: Is it possible with the C# repo to capture data from whole objects (using the type definition or otherwise) instead of having to read every single node manually using its address? (read("node address"))

Alternative question: What's the use of even adding a type definition if it can't be leveraged in a consumer? Is it a comfort for PLC programmers ?

Dear OPC UA community!

I want to develop an OPC UA client for our software using examples from OPC Foundation and MS Azure. I am concerned about the difference between these examples. In the first example, reconnecting after a KeepAlive failure is performed using ReconnectHandler: