did you try deleting all of the asp.net cache

I could not believe this problem has been reported since 2006!

It happened on my win 2003 today.. (this server always has the latest patches).

What I did to fix it was update the code (with some dummy text, or just type a few spaces and delete it back, then save) to force recompile of the code.

Hope it will not happen again or I will be really mad lol.

I havent had the time to read all the posts on this tread. So at this moment I dont know if there is a permanant fix for this issue.

Hoeever for me deleting the temporary files and restarting IIS fix the problem for a while but it keeps coming up.

Hope this will be helpfull to someone who is seeing the error, I@ll try and read the posts to find out if there is a permanant solution.

As far as I know the issue has not been really solved yet. Neither there has been any feedback from any M$ guy as well.

In my case, I narrowed down the problem to those assemblies that contain textual resources such as embedded javaScript files, which are loaded from client via the WebResource or ScriptResource handler. Other assemblies that do not contain such resources have never caused the error until now.

I wonder what makes assemblies with javascript or other resources that difficult to keep being loaded correctly by the CLR!?

Has somebody faced similar issues yet?

As you can tell from looking through the numerous posts here, there are many different scenarios that can cause this, and it happens in many different circumstances. If you're having this issue, you would be best off to open a support incident with us so that we can look into it.

Jim 

Yes, please take some time to contact Microsoft and work on your issues.  We did and were able to resolve this problem once and for all.  After Microsoft determined the cause was due to their code, we were refunded the cost of the support ticket.  If you go back through this thread, starting on 17 Oct 2006, you can see how it played out.  We also used the hotfix I linked on 19 Dec 2007.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;934839

Crazy old issue.  I've been getting the same problem.  The hotfix didn't work.  I found I had to make changes to the code, resave, rebuild and cross my fingers.