I think the logic of "s_settingsFactory", vers. 3.2. and 4.x in SmartStore.Core.Data.DataSettings does not work: I understand the sense that the SettingsFactory supports the use of a own derivative of DataSettings. Unfortunately the private constructor prevents the derivation of DataSettings. If the constructor is made protected and SetDefaultFactory is used, a run time exception occurs later in public static DataSettings Current due the "lock (s_rwLock.GetWriteLock ())" in SetDefaultFactory. Has a mistake actually crept in here? Would you please correct it?
Thanks and Best regards, Wlady