Re: Basic permission attribute question: RequestRefuse
From: Eugene V. Bobukh [MS] (eugenebo_at_online.microsoft.com)
Date: Fri, 25 Jul 2003 13:15:05 -0700
When you refuse any of the permissions, the assembly grant set is not Unrestricted anymore. If the assembly contains some APIs that require Unrestricted security in order to run, you'll get the SecurityException even if you don't use FileDialog.
-- Eugene V. Bobukh This message is provided "AS IS" with no warranties, and confers no rights. Any opinions or policies stated within it are my own and do not necessarily constitute those of my employer. ---- "Keith Patrick" <email@example.com> wrote in message news:%23CYOP%23oUDHA.firstname.lastname@example.org... > I have a Windows service that will not run if I have the following line in > my code: > [assembly:FileDialogPermissionAttribute(SecurityAction.RequestRefuse, > > Unrestricted = true)] > > > > For some reason, I cannot see why the above code would raise a > SecurityException, as I never use a FileDialog. In fact, this behavior > happens for every permission I try it on. Could someone explain to me why > this is the case? As best I can tell, Unrestricted is a problem, but I'm > just not seeing how, though. > >