ASP.NET: Strong named assemblies should not be stored in the bin directory

ASP.NET: Check your Web Site today for these common assembly related memory and perf issues

If broken it is, fix it you should — Thu, 13 Apr 2006 01:37:44 GMT

Recently my colleague Doug wrote a nice post on Nine tips for a healthy "in production" ASP.NET application....

re: ASP.NET: Strong named assemblies should not be stored in the bin directory

Chris — Thu, 13 Apr 2006 04:07:38 GMT

http://www.gotdotnet.com/team/fxcop/docs/rules.aspx?version=1.32&url=/Design/AssembliesShouldHaveValidStrongNames.html

Una serie di link sulle performance Asp.Net

PhilloPuntoIt — Thu, 13 Apr 2006 13:33:57 GMT

Interesting Finds

Jason Haley — Thu, 13 Apr 2006 14:16:27 GMT

re: ASP.NET: Strong named assemblies should not be stored in the bin directory

Dan McKinley — Thu, 13 Apr 2006 20:16:09 GMT

Since you say 1.1 specifically, can I assume this is fixed (ie, /bin assemblies loaded differently) in 2.0? I think complying with the GAC recommendation is probably a bigger headache for people than you realize.

re: ASP.NET: Strong named assemblies should not be stored in the bin directory

Neyah — Thu, 13 Apr 2006 21:23:14 GMT

Does this mean that if two different AppDomains load the same signed DLL that is not in the GAC, that they will share code since the load actually happens in the domain neutral AppDomain? Or will there be two copies loaded?

Also, if I load assembly StrongNameNotInGac.dll then my AppDomain recycles and I load StrongNameNotInGac.dll again, are there now two copies of StrongNameNotInGac.dll in the domain neutral AppDomain, or just one? If there are two, does this mean that the memory taken by the N through N-1 loaded assemblies are "leaked" until the process restarts/recycles?

You specifically pointed out that this is a problem for ASP.NET 1.1. Has anything changed in 2.0?

Based on the FxCop rule that Chris linked to above, I would venture to say that a fair portion of the ASP 1.1 applications deployed here have strong named assemblies in the bin directories :(

Link Listing - April 15, 2006

Christopher Steen — Sat, 15 Apr 2006 07:57:50 GMT

[JS/CSS] event:Selectors - the simplest way to hook
Javascript events to a CSS class [Via: Jon
Galloway...

ASP.NET Performance Checks

Javier G. Lozano — Sat, 15 Apr 2006 21:21:15 GMT

ASP.NET Performance Checks

Javier G. Lozano — Sat, 15 Apr 2006 21:28:45 GMT

re: ASP.NET: Strong named assemblies should not be stored in the bin directory

Tess — Sat, 15 Apr 2006 23:13:32 GMT

Dan,

In 2.0 the assemblies are not loaded domain neutral so you are right:) there was a very specific reason i mentioned 1.1. (and 1.0 for that matter)

Neyah,

If you have two strong named assemblies in different directories they are still loaded twice... ASP.NET still wont know that its the same assembly.

You should not run into the assembly leak you are asking about though... only one dll per unique dll path/name, but i think the question is very valid and i love when people question things like that...

.NET 点滴

子陵 — Sun, 16 Apr 2006 19:19:04 GMT

Ensure that strong named assemblies are not loaded from your bin directory!

Stefan Goßner — Fri, 28 Apr 2006 16:57:44 GMT

Tess explains in detail why you should not place a strong named assembly into the bin directory of your...

re: ASP.NET: Strong named assemblies should not be stored in the bin directory

Karl Costenbader — Fri, 28 Apr 2006 23:15:05 GMT

Tess, this may seem unrelated, but your blogs have really got my wheels spinning:

We have several different applications that our customers can install, each of which has a minimum of 4 different applications (a web client, an application layer hosted in IIS, and a couple of win forms applications). In many cases, the applications are spread over multiple physical machines.

All of our applications share a set of common DLLs that we have written, but based on customer installation cycles and application distribution patterns, they could have numerous versions of the common DLLs in the GAC at the same time. For this reason, we have completely shied away from usnig the GAC, but I am becoming more convinced by the day that we need to bite the bullet and start installing to the GAC.

I am going to assume that you are strongly in favor of installing the common DLLs to the GAC. If so, do you have any pointers/articles on versioning the DLLs or should we just let the compiler pick the next revision number and be done with it? I'm probably overthinking this, but I spent way too much time straightening out DLL versioning issues in the "good old days" to feel completely comfortable about the GAC yet.

Any tips you can provide would be much appreciated.

.NET Resources

mattonsoftware.com — Sat, 06 May 2006 11:30:54 GMT

The following links to .NET resources have been collated over time with the assistance of colleagues.&nbsp;...

Блог баги и отладку

«XOR's Post» — Thu, 11 May 2006 12:56:11 GMT

Рекомендую почитать блог &laquo;If broken it is, fix it you should&raquo;. Детально рассматриваются различные...

re: ASP.NET: Strong named assemblies should not be stored in the bin directory

JohnL — Tue, 23 May 2006 22:55:22 GMT

Tess;
We're running .Net 2.0 and still have this problem.
Is this supposed to be fixed in 2.0?

BTW: the "PRB: "Access Denied" Error Messages..." article you linked to says it applies to .Net 2.0

re: ASP.NET: Strong named assemblies should not be stored in the bin directory

Tess — Wed, 24 May 2006 11:13:46 GMT

Yes, the issue is due to the dlls being loaded in the shared domain in 1.0 and 1.1. which no longer occurrs in 2.0 so i would say that your issue must be due to something else.

re: ASP.NET: Strong named assemblies should not be stored in the bin directory

deniz mert edincik — Sun, 28 May 2006 12:57:10 GMT

tess, about application recycling;

what actually happens when application is recycled... we had an issue like logging under bin directory, which caused one of our web services to recycle on each request...

but I am not sure, is it only performance related or some of the requests can be lost?

thanks in advance

deniz aka bluesign

re: ASP.NET: Strong named assemblies should not be stored in the bin directory

Tess — Mon, 29 May 2006 10:08:07 GMT

Hi Deniz,

The requests that are currently executing will finsih executing but sessions will be lost for example on application restarts.

Tips for a healthy ASP.NET application in production » Advanced .NET Debugging

Tips for a healthy ASP.NET application in production » Advanced .NET Debugging — Thu, 11 Jan 2007 22:22:11 GMT

PingBack from http://dotnetdebug.net/2006/04/15/tips-for-a-healthy-aspnet-application-in-production/

Are you profiling your application and now you can't debug anymore?

A developer's strayings — Sun, 06 May 2007 01:11:48 GMT

This is an interesting case I got very recently and that made me scratch my head a lot, wondering what