(Security) Full trust programmatically - caspol not suitable


G

Guest

Hello,

I'm trying to find a way to programmatically apply a Full Trust policy to a
URL (e.g. http://server/path/path/bin/debug/myassembly.dll). The assembly is
-not- strongly named, because it uses an Excel interop component which cannot
be strongly named.

Up until now I've been having users use Start, Control Panel, Administrative
Tools, .NET Framework 1.1 Wizards, Trust an Assembly - works fine every time,
though it has to be repeated any time the assembly is changed on the server.

I thought I could use caspol for this - but it insists that the assembly
must be strongly-named! The Wizard doesn't demand this, why should caspol??

If anyone could let me know of any ideas, suggestions, it would be very much
appreciated.

Thanks,

Kieren Johnstone

(e-mail address removed)
 
Ad

Advertisements

G

Guest

By default, when you use Interop, it is strongly named, at least if you use
the add references method of adding. YOu also have the option of strongly
naming in the IDE:
http://weblogs.asp.net/mreynolds/archive/2003/07/21/10356.aspx - components
http://weblogs.asp.net/mreynolds/archive/2003/07/21/10353.aspx - ActiveX

More official word:
http://www.gotdotnet.com/team/xmlentsvcs/esfaq.aspx#12.1

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top