Re: shimming, signing and multiple assemblies
- From: v-phuang@xxxxxxxxxxxxxxxxxxxx ("Peter Huang" [MSFT])
- Date: Fri, 26 Aug 2005 06:11:38 GMT
Hi
I recommend you strongname all the other assemblies, because Types in
strong-named assemblies can be called by partially trusted code only when
the assemblies have been marked with the AllowPartiallyTrustedCallers
attribute (APTCA).
NET Framework Assemblies and the AllowPartiallyTrustedCallers Attribute
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/ht
ml/aptcatypes.asp
That is to say, assume there is a type defined in COMAddin
assembly(strongnamed), and the other assembly, which is not strongnamed
wants to call the type, you must marked the COMAddin assembly with APTCA,
which is not recommended.
But if the other assembly will not call the strongname one, you may just
leave them out.
Best regards,
Peter Huang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- Follow-Ups:
- References:
- shimming, signing and multiple assemblies
- From: Alex
- RE: shimming, signing and multiple assemblies
- From: "Peter Huang" [MSFT]
- Re: shimming, signing and multiple assemblies
- From: Alex
- shimming, signing and multiple assemblies
- Prev by Date: Shimming questions
- Next by Date: RE: All public classes are registered for COM interop?
- Previous by thread: Re: shimming, signing and multiple assemblies
- Next by thread: Re: shimming, signing and multiple assemblies
- Index(es):
Relevant Pages
|