Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
For example, in Firefox, there is a plugin-container.exe which isolates Adobe Flash, Apple Quicktime or Microsoft Silverlight plugins so that when they crash, the browser does not crash.
Is it possible to achieve something similar in WPF? Like loading some user-customized controls (analogous to plugins in browser) in a separate process, and make them start their threads (like click handler etc) in that process so that when their code throws an exception, the host application doesn’t crash?
Assuming I have understood your question properly I think this might be considered as a duplicate of
Create a WPF "control" that is run in an external process
The canonical term for this would be “out of process” so you will havemore success if you use this when searching for further information.
These links should get you started
Hosting WPF UI cross-thread and cross-process
Hosting Out-of-process ActiveX control in WPF
AppDomain Isolated WPF Add-Ins