Re: From ASP.NET 1.1 to 2.0:

From: Dominick Baier [DevelopMentor] (dbaier_at_pleasepleasenospamdevelop.com)
Date: 11/16/05 

Date: Wed, 16 Nov 2005 02:09:23 -0800

Hello mlfblom@gmail.com,

your hoster has also set the web sites to partial trust during the update
(a wise decision).

Only assemblies that have the [AllowPartiallyTrustedCallers] attribute can
be called from partially trusted code. This does not seem to be the case
here.

---------------------------------------
Dominick Baier - DevelopMentor
http://www.leastprivilege.com

> Hi,
>
> Recently, my hosting partner (shared hosting) updated my account from
> .NET 1.1 to 2.0. After this update one particular call to a DLL
> (freeware Metabuilders FirstFocus) results in an error:
>
> System.Security.SecurityException: That assembly does not allow
> partially trusted callers
>
>> From the info that I found on www and usenet, this means that my
>>
> partially trusted web app is referencing a strongly-named assembly
> Firstfocus.dll and that is not allowed. I also read that this
> mechanism is also in place for .NET 1.1 but I had never seen this
> before as it all worked fine.
>
> My questions
> 1. why did I not have this issue with .NET 1.1?
> 2. what can I do about it?
> Thanks,
>
> Mark
>

Relevant Pages

  • Anything Wrong With "preloading" Assemblies?
    ... Web sites I maintain on the same server have slightly different ... Some Web sites will need to use the functionality in some ... assemblies, while others will get similar functionalilty from different ... would load the assemblies via Reflection ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Anything Wrong With "preloading" Assemblies?
    ... Use inheritance and a class hierarchy to 'point' to the functionality. ... Some Web sites will need to use the functionality in some assemblies, while others will get similar functionalilty from different assemblies. ... What I was thinking about doing - and I'd apprecaite your feedback on this - is to load the assemblies required by a particular site into the site's default application domain, and do this loading during Application_Start. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Anything Wrong With "preloading" Assemblies?
    ... Some Web sites will need to use the functionality in some assemblies, while others will get similar functionalilty from different assemblies. ... What I was thinking about doing - and I'd apprecaite your feedback on this - is to load the assemblies required by a particular site into the site's default application domain, and do this loading during Application_Start. ... Are there any significant downsides to doing it this way, or reasons I should not preload these assemblies? ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Referencing Assembly Question Without GAC?
    ... You could use assemblyBinding in the .config file to specify a ... Outside of the bin the assemblies are locked. ... >if I could have all web sites use 1 certain web sites bin as the assembly ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: shimming, signing and multiple assemblies
    ... I recommend you strongname all the other assemblies, ... NET Framework Assemblies and the AllowPartiallyTrustedCallers Attribute ... But if the other assembly will not call the strongname one, ...
    (microsoft.public.office.developer.com.add_ins)