Vibrant discussion about CSLA .NET and using the framework to build great business applications.
Are there any recommendations on how to store data locally for metro apps when connectivity isn't avaiable (for occasionally-connected apps)? I've seen a few references online about using Managed Esent as well as just serializing your own objects to local storage. Within the CSLA-world, is there a preferred approach to handling occasionally-connected metro apps? Thanks.
Tim
Any local Storage technique should work fine with the local data portal. The point of CSLA is that it is agnostic to all data Storage techniques.
You should be aware that I am reworking the local data portal to be simpler, and to support async/await, so the next prerelease will be different than the current implementation.
Rocky