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.
Originally posted by @DriftInCode in #4860
Todo:
- Relax key of
NameValueListBase to allow nullable keys.
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.
Originally posted by @DriftInCode in #4860
Todo:
NameValueListBaseto allow nullable keys.