Hi,
The approach you mentioned of using EventAggregator would be correct. However, I don't completely understand what do you refer by having the ViewModels and DbContext disconnected when the ViewModels get the data by calling the DbContext's methods.
Anyway, regarding data consistency, the use of one only DbContext with a big load of data would depend on the complexity for managing the DB and maintaining its consistency. You should try to keep coherence in DB's data and try to avoid extra filters on information requests.
Regards.
Gabriel Ostrowsky
https://blogs.southworks.net/gostrowsky
The approach you mentioned of using EventAggregator would be correct. However, I don't completely understand what do you refer by having the ViewModels and DbContext disconnected when the ViewModels get the data by calling the DbContext's methods.
Anyway, regarding data consistency, the use of one only DbContext with a big load of data would depend on the complexity for managing the DB and maintaining its consistency. You should try to keep coherence in DB's data and try to avoid extra filters on information requests.
Regards.
Gabriel Ostrowsky
https://blogs.southworks.net/gostrowsky
