Security problems with remoting

When I load an assembly (located remotely) that uses remoting, it gives an exception whenever I do any remote calls using it saying I need to set the security for this assembly in the security policy.

It runs ok once I set it using the .Net Wizard o give the assembly full trust.

But whenever I recompile the assembly i need to go and set the security to give full trust to the assembly using the wizard again.
It's a pain. And i can only imagine the pain when I want to deploy the app to remote users.

Is there any way for the main app to be able to set the security to give full trust to the remote assembly automatically?