Hi everyone,

I understand that there's no way to run .NET compiled code from a
network share without security modification but here's my issue - the
code needs to run on a number of workstations (50 or more) and having
each one modify their individual workstations would be an
administrative concern (the company is rather large and individual
workstation changes are frowned upon). Many of the workstations are
locked down, anyway.

Instead of using CASPOL or the .NET Configuration MMC, can the security
be granted on the server side (i.e., the server where the assemblies
reside)? This way we don't have to touch ANY workstation and
administration is easy.

Thanks in advance!

- Shacker

On 16 Aug 2005 07:09:12 -0700, "Shacker" <(E-Mail Removed)> wrote:

¤ Hi everyone,
¤
¤ I understand that there's no way to run .NET compiled code from a
¤ network share without security modification but here's my issue - the
¤ code needs to run on a number of workstations (50 or more) and having
¤ each one modify their individual workstations would be an
¤ administrative concern (the company is rather large and individual
¤ workstation changes are frowned upon). Many of the workstations are
¤ locked down, anyway.
¤
¤ Instead of using CASPOL or the .NET Configuration MMC, can the security
¤ be granted on the server side (i.e., the server where the assemblies
¤ reside)? This way we don't have to touch ANY workstation and
¤ administration is easy.

No, security cannot be granted from the server side because the assembly executes on the client.

The following thread has a code method if that is of any help:

http://makeashorterlink.com/?B227121AB


Paul
~~~~
Microsoft MVP (Visual Basic)

Paul,

I appreciate your reply! I went through the code and tried it on a
couple of assemblies and so far so good! The assemblies are written in
C# so I did some minor language conversion.

Thanks again for your assistance!