cmrnp
asked on
Unable to load assembly when using Caspol
I am getting an error - Error: unable to load assembly when using Caspol.
Background: I have the 1st part of this in Assembly zone but did not realise this was not for .net assembly but Assembly programming. ( please refer Error on startup of mapped network application for full problem ).
Summary: I have received an error when trying to run .net application from a Network drive. It runs fine on my local drive. I understand that this is to do with permissions.
I have used sn to create strong named assembly and copied it to the network location.
I then used caspol -m -af k:\my folder\my app\myapp.exe and receive Error: unable to load assembly.
Can anyone please tell me what I am doing wrong?
Thanks
Background: I have the 1st part of this in Assembly zone but did not realise this was not for .net assembly but Assembly programming. ( please refer Error on startup of mapped network application for full problem ).
Summary: I have received an error when trying to run .net application from a Network drive. It runs fine on my local drive. I understand that this is to do with permissions.
I have used sn to create strong named assembly and copied it to the network location.
I then used caspol -m -af k:\my folder\my app\myapp.exe and receive Error: unable to load assembly.
Can anyone please tell me what I am doing wrong?
Thanks
ASKER
Sorry, as it is a clients machine.
I don't want all intranet programs to have full trust.
Thanks anyway.
I don't want all intranet programs to have full trust.
Thanks anyway.
What is the Membership Condition for the trust?
Bob
Bob
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I attached a screen shot of what I mean by the membership condition tab
Bob
Membership-Condition.png
Bob
Membership-Condition.png
ASKER
We seem to have gone off the initial question so I am closing the question.
It has been decided to install it on client's C: drive.
The initial question's solution was to have quotes around the path as it had spaces.
Sorry I couldn't award any points.
It has been decided to install it on client's C: drive.
The initial question's solution was to have quotes around the path as it had spaces.
Sorry I couldn't award any points.
2.0-.NET-Framework-Configuration.png