If I have an entity Entity and a service EntityService and EntityServiceFacade with the following interfaces:
I need to load an untrusted assembly into my AppDomain. I don\'t want to Sandbox a new AppDomain for this assembly to execute in, because it internally requires access to certain functionality such as
I am looking for a simple and secure way to access plugins from a .NET application. Although I imagine that this is a very common requirement, I am struggling to find anything that meets all my needs:
Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow.
I have just read about this article about Code Access Security. It has such an example in it: using System.Security.Permissions;
The use case: I have a hosting platform (server) where multiple ASP.Net applications are hosted. I do not want to have application to have programmatic access to the certificates on the Server. Only
I wrote the following code to test the CAS: [SecurityPermission(SecurityAction.Demand,Flags=SecurityPermissionFlag.Execution)]
I am studying the Code Access Security of .NET 2.0. My current understanding is as below: The basic mechanism of the CAS is for the CL开发者_如何转开发R to collect certain evidences from the assembly
In a shell application, I need to be able to load and execute other .NET assemblies at runtime, but without giving them full trust. Essentially, I want to limit them (the loaded assemblies) from touch
I have a custom action that I\'m using to deploy some files that sit next to the msi in the handoff package. My custom action is passed the ms开发者_如何转开发i path via the OriginalDatabase parameter