Hello.

In general, we expect our users to work with types that are documented in the Reference section of the documentation, and nothing else.
There are many public types that are not documented, and that is intentional (a lower layer assembly exposes them for higher layer assemblies, but they are not intended for our users).

For this reason, anything that changes but is not documented in the Reference should not be a breaking change to our users.

I have not checked whether this particular types had previously shown in the Reference, but I believe it had not. So the change of the namespace would be internal to us. If it had been shown in the Reference, please accept my apology - but in that case it was an oversight and that's why it has been moved.

I understand that this particular type contains useful methods. Feel free to use them - but without guarantee. In fact, in the future we might consider exposing the type  (*and* documenting it at the same time) - in which case it would change the namespace again.

Regards
 

In version v5.82 and prior, the IDictionaryExtension class was in namespace OpcLabs.BaseLib.Collections.Generic.Extensions and has been a publicly accessible type since I've been working with QuickOPC.  In the latest v5.83.477, I notice this IDictionaryExtension class is still publicly accessible but is now located in namespace OpcLabs.BaseLib.Collections.Generic.Internal.Extensions.  This is an unexpected breaking change on a minor version bump between v5.82->5.83.  

What might be the reason for this and is the "Internal" addition to the namespace of this class an indication that it may not longer be publicly available in future releases?  I would expect a change of this type to require a major version bump.