We have a strange issue with our C++ solution (which calls .NET 4.0 assemblies) when running on a network drive. The solution hosts several WCF services with NetTcpBinding, one of them with a non-default binding configuration. A non-default NetTcpBinding is per se not possible under partial trust (see Stack Overflow question When does WCF NetTcpBinding need full trust on the client?), but the solution runs under a fully trusted network drive. This does work on several different computers (Windows Vista and Windows 7) but fails on one (Windows Vista) with throwing an exception,
An error occurred creating the configuration section handler for “system.serviceModel/bindings”: That assembly does not allow partially trusted callers. (K:\Somepath\Testing.exe.Config line 6)
This exception would be totaly OK, if the solution would indeed run under partial trust on that computer, but it does run under full trust. Even if I check for full trust in code it is true.
We double checked the Internet options with one of the computers it works on – no differences.
All DLL files and the EXE file are strong named.
Update:
The network drive is under full trust on the particular computer (caspol.exe).
What should we look for?
If you need additional information, please let me know.
Update 2:
We still have that issue and now even on one computer more (Windows 7). So it seems to be OS independent.
We didn’t find a solution here but a workaround: Don’t use the app.config for the binding settings. Setting them in code works for us in the same environment.
This question by the way seems to handle a similar issue. HTH