To verify the prior posts results and ensure this wasn't due to something in my particular CS-
- I created a new CS 2/Asp.Net 2.0 website (local and remote) and new database (remote). The app functions as expected.
- I applied the CuteChat 3.1 install to local (and sql to remote DB)... Local works as expected.
- I added the Medium Trust element to the local Web.config.. the local website/CuteChat fails with aforementioned errors.
- I replaced the 3.1 dll with the dll downloaded from above post.. local/CuteChat functions as expected (web.config/Medium)
- I removed the Medium Trust from web.config and uploaded/applied local CuteChat to remote... remote fails.
The following is CT's words about trust:
To protect our shared environment, we have set the CAS Level to Custom. The custom setting is basically medium level with some exceptions including ODBC, OLEDB, sockets, Reflection Permissions and Web Permissions. This setting cannot be overridden.
Here are the permissions granted by the medium trust level:
Medium
Permissions are limited to what the application can access within the directory structure of the application.
No file access is permitted outside of the application's virtual directory hierarchy.
Can access SQL Server
Can send email by using SMTP servers
Limited rights to certain common environment variables
No reflection permissions whatsoever
No sockets permission
To access Web resources, you must explicitly add endpoint 'URLs' - either in the originUrl attribute of the
element or inside the policy file.
The following exceptions have been granted in addition to the ones listed above:
ODBC
OLEDB
Reflection Permissions
Web Permission
What to do?
D