<!--- Questions: If you have questions about how to use Realm, please ask on -->
<!--- StackOverflow: http://stackoverflow.com/questions/ask?tags=realm -->
<!--- We monitor the realm tag. -->

<!--- Feature Request: Just fill in the first two sections below. -->

<!--- Bugs: To help you as fast as possible with an issue please describe your issue -->
<!--- and the steps you have taken to reproduce it in as much detail as possible. -->

<Unable to render embedded object: File (--- Thanks for helping us help you) not found. -->

Goals

Move the Realm exception realm::IncorrectThreadException to .NET Framework VM, so it can be catched using a try catch.

Expected Results

Instead of having the app firmly crash without possibility to recover in case of a thread using the realm object incorrectly, I expect that the behaviour of the app must be controlled: even if I known that, because of the realm limitation, a realm object cannot be shared by threads. An app must have the possibility to catch the exception and continue to work even if the data is lost. For example, an app can log the status or send telemetry to the company, and inform user that something gone wrong and to contact support.