2
steeladeptYour problem can't be solved in BBCeditor easily because it's framework issue and MS security policy.
There are two ways for "fixing" it but they either are troublesome or are something I don't want to do:
- making installer which will change security policies on PC;
- make non-.NET loader which will do the same dynamically;
Both ways require same things: you have to store them on local PC and run each time you want to use BBCeditor.
How does it differ from current situation? You have to copy something to local machine and you will loose it after restart.
The only way (but not secure) is to have valid network policy set in backup system's image. If your administrator allows to run other executables from network than it should be no difference for him to add a rule for .NET.
That link should explain how to do that:
http://support.microsoft.com/kb/832742