You can use the .Net configuration wizard to weaken security for a particular assembly and its location, which, in turn, can be deployed using Group Policy. You can also use caspol, as mentioned earlier.
Another alternative is to use code access protection. There is a brilliant MSDN article here explaining this.
The third option is to use clickonce deployment, but when it is executed, a local instance of the assembly is created.
source share