Security transparent is good when we control the code what about external DLL?
The security transparent code is good when we control the code but what if get assembly which is a third party. In those situations you can use the concept of sandboxing. One of the important points to note is that CAS is deprecated and not removed completely. So if you have third party DLL you can create your own appdomain and assign permission sets so that your 3rd party DLL runs under a control environment. Below is a simple code snippet which shows how we can do things. The below code snippet, creates an application domain, allocates permissions for execution and user interface display only. We then try to do something funny like popping up a file brows dialog box and we end up with error as shown in the below figure. Step1:- Create appdomain with two permission execution and UI display using permission set class.
