Glenn,
Please refer to the following articles -
http://support.microsoft.com/?kbid=324519
http://support.microsoft.com/default.aspx?scid=kb;en-us;813833
http://blogs.msdn.com/tess/archive/2006/04/13/575361.aspx
These all indicate that running ASP.NET applications with strong
named assemblies deployed to the bin folder is not supported in .NET 1.1
or 2.0 as well as some of the symptoms might be experienced.
Thanks,
Tom
-----Original Message-----
From: GlennDoten [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 21, 2006 10:19 PM
To: Log4NET Dev
Subject: Re: Strong name private key policy
Not true, Tom. Just because an assembly is signed does not mean it
must be in the GAC to be used by ASPX. We run non-GACed, signed
assemblies with ASPX in production all the time.
FYI
On 6/21/06, Whitner, Tom <[EMAIL PROTECTED]> wrote:
> We are facing a similar question with some internal code. We have
> decided, at least for now, to produce both strong named and non-strong
> named binaries. Most agree that the strong named option is preferred.
> However, due to ASP.NET'sbehavior when loading strong named assemblies
> (i.e. it requires the GAC), not all individuals can/will tolerate GAC
> installation on highly locked down server. Hence, having the
non-strong
> versions has become a necessity.
>
> - Tom
