2. EventLogPermission is not available. This means you cannot access the Windows event log.
3. ReflectionPermission is not available. This means you cannot use reflection.
4. RegistryPermission is not available. This means you cannot access
the registry
5. WebPermission is restricted. This means your application can only communicate with an address or range of addresses that you define in the <trust> element.
6. FileIOPermission is restricted. This means you can only access files in your application's virtual directory hierarchy. Your application is granted Read, Write, Append, and PathDiscovery
permissions for your application's virtual directory hierarchy. That is, Medium Trust restricts FileIOPermission in the following manner: "FileIOPermission is restricted. This means you can only access files in your application's virtual directory hierarchy. Your application is granted Read, Write, Append, and PathDiscovery permissions for your application's virtual directory hierarchy. You are also prevented from calling unmanaged code or from using Enterprise Services." A script will only be able to run FileIOPermission operations on files within it's own virtual dir and subfolders, not outside them. In this case, the script calling FileIOPermission operations will need to actually save the file in the same folder as the script or a subfolder of the script's current folder.
7. You are also prevented from calling unmanaged code or from using Enterprise Services.
TIP: When testing your ASP.NET site locally on your own machine, you can test the security level that your ASP.NET site will run in. The instructions on how to check and configure your own IIS's web server trust level is available online at http://msdn2.microsoft.com/en-us/library/ms998341.aspx
NOTE: For additional ASP.NET support and resources we recommend the following web sites: