Re: CAS and Office Development.
From: Nicole Calinoiu (calinoiu)
Date: 06/18/05
- Previous message: Nicole Calinoiu: "Re: Application security"
- In reply to: Scott Gauthier: "CAS and Office Development."
- Next in thread: goot: "Re: CAS and Office Development."
- Reply: goot: "Re: CAS and Office Development."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sat, 18 Jun 2005 07:56:34 -0400
"Scott Gauthier" <-> wrote in message
news:ejMQGd4cFHA.1276@tk2msftngp13.phx.gbl...
<snip>
> BTW:
> I have all the frameworks installed on it: 1.0, 1.1 and 2.0, not that
> this should matter but I figured I would throw it out there anyways...
That might actually explain the problem. Both the CAS policy and CAS
enabling/disabling (via caspol -s off) are version-dependent, and I'm
guessing that your policy reset and/or CAS disabling weren't applied to the
same version of the framework as is actually loading the assembly. I
haven't tried running a VSTO app on a multi-version install before but, if
it's anything like an IE-loaded assembly, there's probably no way to choose
the target Framework version. If so, it's probably being loaded in v.2
regardless of which version you used to code it. If altering the v.2 policy
doesn't work, try making the same policy alteration for all versions.
- Previous message: Nicole Calinoiu: "Re: Application security"
- In reply to: Scott Gauthier: "CAS and Office Development."
- Next in thread: goot: "Re: CAS and Office Development."
- Reply: goot: "Re: CAS and Office Development."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|