Hi! We have a little tool that need to run from a network path. it's a little exe file in a specific place. I've created a strong name key and signed my assembly with it in .net 2005 (Framework 2.0) I did it already with .net 2003 (Framework 1.1) and after I've configured the security in "Microsoft .Net Framework 1.1 Configuration" it was working fine from the network path. I've modified, Runtime Security Policy, Enterprise, Code Groups, All_Code to add my company name configuration set. I've checked the two box in the General Panel. I've chosen the Strong Name and imported the key from the assembly. I've pick the "FullTrust" Permission Set. I then created a deployment package and apply it on the required machine prior to run the assembly. I've did the same thing in Framework 2.0 because we needed to support Windows XP x64 and modify the registry in 64 bit registry. The assembly works fine from a local drive but when I put it on the network, the program crashes. It now run fine on my Windows XP x86 from the network drive. I've compiled it for anyCPU in .NET 2005 But when I try it from the Windows XP x64 computer with Framework 2.0 (x64) it crashes. I've installed the Framework SDK to configure the security on the x64 machine, I redo the whole security configuration but it still crashes. How can I solve this issue, this application is really critical for us... Thanks a lot! Fred I did the same thing in
