NameValueListBase in CSLA 10

[DriftInCode]

As we were upgrading to .NET 10/CSLA 10, we noticed that all of our value lists that inherited from NameValueListBase had errors. What we realized is that the definition had changed where it no longer allows null values for K, V. Most of our value lists are <int?, string> to support the cases where the value could be optional (so we store NULL on the database side). Since null values are no longer allowed in NameValueListBase, what is the recommended approach? The last thing we want to do is abandon the use of NameValueListBase and have to implement a completely new approach using something like ReadOnlyListBase.

[rockfordlhotka]

This is probably from the work done by @StefanOssendorf, he should be able to provide some insight.

[StefanOssendorf]

Hi. I based this on the Dictionary<T, K> implementation, where at least the key is not null. That's why I did the same here. But I don't see any reason why we couldn't relax that restriction.
Do you need this only for the key, or for the value as well?

[DriftInCode]

For our implementation, it's only the key that is potentially null.

[StefanOssendorf]

Okay, thanks. I hope I can get to that today or tomorrow. It will be done 👍🏻