Hello.
In OPC UA, all reference types are identified by reference type IDs, which are just OPC UA Node Ids. The reference types are not really identified by "names". Names only exist to assist humans in writing and reading the documentation (there are BrowseNames and DisplayNames in OPC UA, too, but they do not uniquely _identify_ anything, they always has to work in context of other :parent" node).
What you see in UAReferenceTypeIds class may look like this is a list of reference type "names", but they all just return UANodeId-s. The "names" comes form the OPC UA specification, in this case, because the purpose of the UAReferenceTypeIds is to make it easier for users to obtain the Node Id of the reference type when typing in the code, without having to hard-code the Node Id, which in case of standard reference types is always an integers, so it's not really something people can remember or easily work with.
So, any other reference type is not different : It will be represented by Node Id again, not by any "name". In your case, you can test whether the returned ReferenceTypeId equals to the reference type Id you want, and it may look something like this:
if (nodeElement.ReferenceTypeId == new UANodeId("http://statusenterprise.com/StatusServer/User", 4008)
{
///
}
I do not understand how the reference type Id could be "different" in other OPC UA server. If the same reference type is meant to be used over multiple servers, then it must have the same Node Id. For example, when OPC Foundation defines a reference type, whenever somebody wants to use, he will use it - and it will have the same Node Id. If somebody has defined your "HasAliasTarget", it should have given it a Node Id, that is: a namespace URL, and an identifier (integer, string, GUID, or opaque). And it must stay the same always, otherwise it would not be the same reference type.
If the Node Id of your reference type "changes", then you cannot look for answer it in the OPC UA specifications, and you cannot look for answer in the toolkit you use (QuickOPC, in this case). You need to resolve that problem with whoever "defines" such reference type.
Best regards
