ZoneSandboxAppDomainManager.cshttp://blogs.msdn.com/b/shawnfa/archive/2004/11/17/259103.aspx1 using System; 2 using System.Reflection; 3 using System.Security; 4 using System.Security.Policy; 5 6 namespace AppDomainManagers 7 { 8 public sealed class ZoneSandboxAppDomainManager : AppDomainManager 9 { 10 private AppDomain internetDomain = nullen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)re: ZoneSandboxAppDomainManager.cshttp://blogs.msdn.com/b/shawnfa/archive/2004/11/17/259103.aspx#9968864Wed, 24 Feb 2010 20:21:23 GMT91d46819-8472-40ad-a661-2c78acb4018c:9968864shawnfa<p>5 years later, we now ship frameworks such as the Managed Extensibility Framework and Managed AddIn Framework that take care of lots of the security and versioning issues for you. &nbsp;I would recommend checking those out to see if they meet your needs before rolling your own implementation.</p> <p>-Shawn</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9968864" width="1" height="1">re: ZoneSandboxAppDomainManager.cshttp://blogs.msdn.com/b/shawnfa/archive/2004/11/17/259103.aspx#9950549Tue, 19 Jan 2010 21:40:28 GMT91d46819-8472-40ad-a661-2c78acb4018c:9950549Merritt Graves<p>5 years later, would you still use this approach for loading untrusted 3rd party plugins, or would you recommend a different approach to sandboxing an app domain? </p> <p>I have a scenario where I am writing code that is explicitly responsible for loading code written by untrust(ed/able) 3rd parties.</p><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9950549" width="1" height="1">Customizing the AppDomain Creation Processhttp://blogs.msdn.com/b/shawnfa/archive/2004/11/17/259103.aspx#259115Wed, 17 Nov 2004 23:38:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:259115.Net Security Blog<div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=259115" width="1" height="1">Customizing the AppDomain Creation Processhttp://blogs.msdn.com/b/shawnfa/archive/2004/11/17/259103.aspx#259110Wed, 17 Nov 2004 23:36:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:259110.Net Security Blog<div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=259110" width="1" height="1">