windows
Giving FullTrust permissions to the .NET assemblies at network shares
I have Virtual PC machine with Windows XP and .NET 2.0 and I need to start .NET application from the shared folder which is mapped to Z drive letter. But the application executable gives me "Application has encountered a problem and needs to close." dialog right after start.
I've tried to compile it with MSBuild from sources on Z: and it have displayed the following error:
... System.Security.SecurityException: That assembly does not allow partially trusted callers. ...
Aha, incorrect permissions! MSBuild does not want to load and execute logger assembly from mapped drive because it is in the Intranet zone, which does not allow full trust. It looks like the application executable could not be started because of the permissions too. So how to give allow assemblies from mapped network shares run with FullTrust permissions?
As I have read this can be done in two ways: by configuring permissions in mscorcfg.msc, or by modifying code access security policy with caspol.exe.
Because mscorcfg.msc is not included in .NET 2.0 redistributable I've executed the following command in the Run dialog (Win+R) to allow assemblies from mapped networking shares run with FullTrust permissions:
c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\caspol -q -machine -addgroup 1 -url file://z:/* FullTrust -name "Z Drive"
Works perfect.
Annoying system restart notification after installing updates
As usual, my Windows XP starts asking me to reboot it after installing new updates. In Vista I can postpone notification for several hours and forget about it, but XP pop ups the notification each several minutes giving me a big chance to shut down the computer and lose my work.
To turn it off just press Win+R and type the following command and press Enter:
net stop "Automatic Updates"
This will completely shot down the automatic updates till the next reboot. Remember that you still need to reboot your computer after completing the work unit to apply the updates - your computer may be vulnerable before reboot.


