6 Comments

  • Very wierd...especially as I have this working for a number of sites???

  • WHOAH MAN! This is important Stuff!



    I have had this error imtermittently for the last 2 years....The best answer I had for it up until was another knowledge base article that stated it another process (like the Indexing Service) was accessing the ASP.NET temp directory this error could happen, which perplexed me because I have seen it on machines with no virus checkers and indexing service disabled....



    Note...If this is the cause, it is not easy to reproduce. But I have defintaly seen it hundreds of time over the last 2 years and have considered it the only critical ASP.NET bug that the team has never gotten on top of.



    I have actually been signing all our critical libraries and installing them into the GAC (instead of the bin dir) just because it ensures this never happens, and we provide SLAs on our production systems to partners.



    Note that when this bug happens it is BLOODY UGLY. Even an IIS 6 Worker Process recycle DOES NOT solve the probelm!



  • David: Thanks for the comment, it sure sounds like a bad one.



    This came to my attention when I got a message from one of our platform support guys. He had found it in the KB and naturally wants to put all our signed DLLs into GAC now, just to be sure and to meet the SLAs.

  • Holy crap, that is mind blowing... what were they thinking?

  • All along I thought signed assemblies are possible in bin directory. This has to do, of course, with versioning. Juval Lowy, in his book "Programming .NET components, p.82", he states that "if the private assembly does contain a strong name, .NET zealously enforces it version compatibility policy." in order to resolve things. Hmm.....

  • What I love is how the knowledge base article says "This behavior is by design".



    My arse it is by design....



    Sure...The ASP.NET team thought "Lets have it work the first time.....but then 1 day later when IIS does a worker process recycle, lets fail it them....yeah that would be a great idea wouldn't it".



    Really....Just admit it is a bug. Either fail immediately or fix the bug!



Comments have been disabled for this content.