Issues raised by Silverlight RIA Services Cache

problem Description: using Silverlight's RIA Services for database update operations, finding exceptions when repeating commits, submitoperation errors, prompting entity class conflicts, Check that the data deleted before the discovery is still there (deleted in the database), and then delete the operation, the database is no longer existing data deleted, so error.

Workaround: Each commit operation is re-load once, to ensure that the data is synchronized with the database, the load data to operate, clear the impact of cached data, the problem is resolved.

Reason: this is because RIA services will each time according to the query criteria of the data in the database is taken out to the client, and into the form of entity classes to facilitate the developer of data additions and deletions, and then through the Submitchange method to submit all operations, the database is updated, This may cause the database to be updated, but the client's data is not updated and an error is raised.

In addition, the issubmitting, isloading status of Domain Services needs to be processed before submission to avoid failure.