Quote:
Have you actually succeded in writing to the registry from a program running over the network? My understanding is that RegistryPermission won't do squat by itself, and the local machine still has to have its security setting set up to allow it.


I did tinker with it a bit more, but never got it working. It does indeed seem to be blocked by a policy in XP SP2 by default. Now, the question is, why have the RegistryPermission class when it is not needed on the local machine, and when running remote fails silently? No exception was generated to say it couldn't gain access, it simply ran right by it and caused the same access denied exception when the code tries to read the registry. .Net is pretty new, and already it seems it has worthless crap scattered in it. I can't find one real world reason to use RegistryPermission now.