Today, when using VSTO for office development, quote the library developed in the codebehind code, but found that the code is not running in this library when debugging, the resulting error message is a security problem, then there is a good idea Because all referenced librays will automatically join the security policy when doing InfoPath development, they think that it is also thinking in Word.
The ultimate fact is that VSTO is only added with the security policy of codebehind.dll in the security policy, which is not a projectname_bin whole directory, so the above-mentioned reference library security issues have occurred.
Join the security policy for this reference library, everything OK.
