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
