.NET container issues
1. Sandboxing code dynamically

Quoted from http://www.dotnetthis.com/Articles/DynamicSandboxing.htm

I have been getting questions from people about how to make a piece of managed code execute in a security restricted environment, or how to "sandbox" it. Some people are trying to use stack walk modifiers (such as Deny()) to do it, which does not work for this purpose. Other people are trying to modify the machine security policy (which when done correctly works) or put an application in question on a network share and run it from there (which also works and gives the application LocalIntranet permissions, if your policy is default). There is however a way to sandbox a piece of code dynamically, by creating an appdomain, setting its security policy and loading an assembly there.


2. .NET remoting in appDomain
Quoted from http://www.codeproject.com/csharp/processactivator2.asp

This article is a follow-up to my previous article entitled: "Simple but potentially useful example of .NET Remoting". In my earlier article, I expounded on basic codes necessary to startup a .NET remoting project. The example code of that article used Server Activated Remote Objects. In this article, we shift our attention to Client Activated Remote Objects which are different from and are often much more useful than server activated ones.
- posted by Pop @ 4:58 PM