Executing .NET Assembly from UNC path
-
Hi all, I am attempting to execute an assembly from a UNC path (e.g. \\sydxyz\share) but I always get the CLR error message "Application has generated an exception that could not be handled". The permissions on the share are correct and I have tried generating the assembly with a strong name, altered security profile etc.. as in the .NET Code Access Security documentation, but to no avail. However, if I map that network share to a drive letter (net use z: \\sydxyz\share) and run the program it works with no problems. I've looked at the Intranet_Zone security etc... etc... and now am suspecting that an Active Directory (global) group policy is somehow getting in the way? Has anyone seen this before or have any ideas where to start? TIA ...Steve
-
Hi all, I am attempting to execute an assembly from a UNC path (e.g. \\sydxyz\share) but I always get the CLR error message "Application has generated an exception that could not be handled". The permissions on the share are correct and I have tried generating the assembly with a strong name, altered security profile etc.. as in the .NET Code Access Security documentation, but to no avail. However, if I map that network share to a drive letter (net use z: \\sydxyz\share) and run the program it works with no problems. I've looked at the Intranet_Zone security etc... etc... and now am suspecting that an Active Directory (global) group policy is somehow getting in the way? Has anyone seen this before or have any ideas where to start? TIA ...Steve
Try this: http://gnonug.xocomp.net/Support/FAQ/85.aspx[^] --Colin Mackay--
EuroCPian Spring 2004 Get Together[^] "You can have everything in life you want if you will just help enough other people get what they want." --Zig Ziglar
-
Try this: http://gnonug.xocomp.net/Support/FAQ/85.aspx[^] --Colin Mackay--
EuroCPian Spring 2004 Get Together[^] "You can have everything in life you want if you will just help enough other people get what they want." --Zig Ziglar
Colin, Thanks, however I managed to trace the problem to be a combination of Framework 1.0 and network shares with spaces in their names (e.g. "\\sydxyz\is share"). There is an undocumented bug in the Framework 1.0 code which has been fixed in 1.1 (ASURT#127619 - obtained from Microsoft support). This is not yet in TechNet or MSDN. ...Steve