Brendan Tompkins [MVP]

nor me - this is one big problem it seems.  Have tried endless reconfiguration after upgrading to the latest ajax asp.net version, but it has completely broken my application...

thanks alot...it works.

I was hooked with this error for two days...

Good work..

cheers

madhu

Delete the Line in which the assembly is loaded from web.config

It has worked for me nothing else was working for hours.

Thanks, Brendan! I got paged at 5:30 AM by one of our ASP.NET sites, and Google + your blog post proved invaluable in getting things up and running again!

- stopped WWW Publishing service

- deleted temp files you specified

- started WWW Publishing service

Thanks again!

Grig

not worket for me

If we're talking about the same error, I've been getting this for years.  If you delete temporary files (or, as the asp.net forum mentions, make a small change to the user control indicated in the error), you force a recompile, and the error goes away.  The *error* goes away, but not the *problem.*

A real "fix" would prevent the problem from occuring -- which it does only sporadically.  I don't know how to reproduce this bug, nor of anyone else who does.  MS can't do anything about it, after all, until it's reproducible.

Para arreglar este error :

Una vez que se publique el Sitio Web, hay que ir al: Servicios de Internet Information Server (IIS), desplegar el menu de la parte izquierda, en este menu donde dice: Sitio Web Predeterminado crear un nuevo Directorio Virtual, se sigue los pasos , se pone un Alias (puede ser el mismo nombre con el que se publico nuestro Proyecto), luego donde sale escoger el directorio, escogemos nuestro sitio web que acabamos de publicar y poner siguiente, siguiente, las opciones que salen por defecto.

Luego ponemos en el URL del Internet Explorer la dirección de nuestro sitio y ya no saldra el error.

En mi caso (trabajando con: Microsoft Visual Studio 2005 y AJAX), con esto pude arreglar el problema de: Could not load file or assembly App_Web ...

I can't believe that MS hasn't provided a real solution for this problem yet. The solution listed here is only a temp solution, but I've only experienced this problem with sites using master pages & nested user controls. Is this the case for everyone else?

I've never gotten an error like this running classic ASP - it has 100% up time. Running SiteScope just to make sure. Should I just skip asp.net 2.0 and wait for a fix. I need to be up 100% of the time. Perhaps this is only related to the compile at runtime style deployment vs. the Asp.net 1.0 approach of precompiling everything.

We have an app being used by our university and this error suddenly shown up after moving to a new server. After months trying every possible solutions from the web... none working for us. Finally, last week the error disappeared completely after we undo the default pool recycling in our IIS .  Hope this would help someone with the same problem.

Cheers,

Just case other people come across this problem and they are using .net 2 to write their app, make sure your IIS setting isn't using 1.1 !!! (yes I know!)

Good!!

It's work for me..m getting this headache from half of the day...thanks...a lot :)

Its' work for me..........Thanks a lot!!!

my error "could not load file or assembly comes up when i start the computer so is not a big problem but an annoyance, checked in the temporary ASP.net files and there was none to delete so fix did not work for me , thanks in advance.

I copied over the new dll's to wherever they appear in the project, I've reregistered my references, I've deleted my temp files, and STILL, the old version is stuck somewhere. I can't figure out where. This is SO frustrating!

Thank you very much for providing solution. It has resolve my similar issue.

Thank you so much..

After a year this artikel. I got similiar problem, and it has been resolved.

A quicker fix would be to enable/disable the "Enable Debugging" checkbox in IIS under ASP.NET > Edit Configuration > Application

Sometimes that we cann't do this action,because we have no acces to the web server.

What if i get the error but the folder mentioned above is empty?

How can i fix it in this case?

Thank you, it worked for me too.

Thanks, this seems to have fixed it for me...

ohhh..yes it solved my problem...helpful....i was hanged by this problem...

Thank you....

Hi guys maybe it could help someone. I had the same problem and what fixed the problem is to :

(1) Remove the AJAX DLL from the references

(2) Add the same AJAX DLL again as a reference

(3) Rebuild the project

i cannot assure that it works, but i worked for me

good luck

It's 4:14 AM here in Israel and I LOVE YOU SO MUCH Brendan!!!!!!

I LOVE YOU I LOVE YOU I LOVE YOU I LOVE YOU!!!

Thanks a lot ... sir.. It solved my problem.

thanks a lot. its working...

Thanks, You helped me :)

I work with Silverlight and WCF Services and I have often this stupid error :/

You've been kicked (a good thing) - Trackback from DotNetKicks.com

Here's how I created and then fixed this problem. I hope it helps someone.

I changed the name of a file.

Then I went in and manually changed the top statement in the aspx (I use separate c# code files)  to reflect the proper: 1) 'inherits' statement and the 'codefile' variable.

I neglected to change the class name in the .cs file.

That was what CREATED the error.

To fix it? I renamed the class name in the .cs file to correspond with my other renamings and... voila. No more app_web errors.

Is this helpful?

Verify the Project property

project property --> build-->platform target

thanks

To resolve the problem, I also took care to use the correct version of the .NET framework:

1. Go to Internet Information Services

2. Go to the virtual directory, right click on it and go to Properties

3. Go to ASP.NET tab, and choose 2.0.50727 in ASP.NET version

Hope this helps

Pingback from  Komputerowe  » Blog Archive   » Problemy i cz??ste b????dy podczas pracy z Silverlight-em . Part 1

thanx a dozenn ...........it worked by deleting files from TempASP.Net files!!

:D

Yah, I've gotten that a bunch actually. Usually it's b/c of temp files.  Clear your temp directory and give it another try. What's happening is that the temp file name generated when the assembly is loaded exceed 255 characters. So it's truncated.  That in turn means that what it's trying to access doesn't exist.  

Here’s a related support kb addressing the issue: support.microsoft.com/.../823196

Also, set the compilation directory's tempDirectory property specifically. You can point it to C:\whatever or some shorter path name than it normally would use and thereby not have the really long path name problem.

Ray Akkanson

I had the root folder configured as a virtual directory to run asp.net application.

The problem was I didn't create the virtual directory under the root thus asp.net was running but couldn't find the correct location of the bin folder.

Add the batch=false attribute to your web.config 'compilation' tag :

   <compilation batch="false" />