Could not load file or assembly App_Web.....

[Almond]

HI people,

I am experience the problem below and tried a lot of fixes and still
didn't work. Can someone take a look and give some hint? thanks so
much.


Could not load file or assembly 'App_Web_f8_lco1l, Version=0.0.0.0,
Culture=neutral, PublicKeyToken=null' or one of its dependencies. The
system cannot find the file specified.
Description: An unhandled exception occurred during the execution of
the current web request. Please review the stack trace for more
information about the error and where it originated in the code.

Exception Details: System.IO.FileNotFoundException: Could not load
file or assembly 'App_Web_f8_lco1l, Version=0.0.0.0, Culture=neutral,
PublicKeyToken=null' or one of its dependencies. The system cannot
find the file specified.

Source Error:

An unhandled exception was generated during the execution of the
current web request. Information regarding the origin and location of
the exception can be identified using the exception stack trace
below.

Assembly Load Trace: The following information can be helpful to
determine why the assembly 'App_Web_f8_lco1l, Version=0.0.0.0,
Culture=neutral, PublicKeyToken=null' could not be loaded.


WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM
\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind
failure logging.
To turn this feature off, remove the registry value [HKLM\Software
\Microsoft\Fusion!EnableLog].



Stack Trace:


[FileNotFoundException: Could not load file or assembly
'App_Web_f8_lco1l, Version=0.0.0.0, Culture=neutral,
PublicKeyToken=null' or one of its dependencies. The system cannot
find the file specified.]
System.RuntimeTypeHandle._GetTypeByName(String name, Boolean
throwOnError, Boolean ignoreCase, Boolean reflectionOnly,
StackCrawlMark& stackMark, Boolean loadTypeFromPartialName) +0
System.RuntimeTypeHandle.GetTypeByName(String name, Boolean
throwOnError, Boolean ignoreCase, Boolean reflectionOnly,
StackCrawlMark& stackMark) +72
System.RuntimeType.PrivateGetType(String typeName, Boolean
throwOnError, Boolean ignoreCase, Boolean reflectionOnly,
StackCrawlMark& stackMark) +58
System.Type.GetType(String typeName, Boolean throwOnError, Boolean
ignoreCase) +64

DBauer.Web.UI.WebControls.DynamicControlsPlaceholder.RestoreChildStructure(Pair
persistInfo, Control parent) +255

DBauer.Web.UI.WebControls.DynamicControlsPlaceholder.LoadViewState(Object
savedState) +209
System.Web.UI.Control.LoadViewStateRecursive(Object savedState)
+251
System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList
childState) +142
System.Web.UI.Control.LoadViewStateRecursive(Object savedState)
+300
System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList
childState) +142
System.Web.UI.Control.LoadViewStateRecursive(Object savedState)
+300
System.Web.UI.Page.LoadAllState() +520
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
+3444

--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.832;
ASP.NET Version:2.0.50727.832

[Joe Enos]

It's possible that this is due to recompiling a website, and not
replacing the .aspx pages. Whenever you rebuild your site, you need
to replace not only the DLLs, but the .aspx pages as well, on the web
server. One of the many disadvantages of using "WebSite" instead of
"Web Application" projects in VS. If that's what's happening to you,
then your solution is just to replace the .aspx pages with the newest
version.

In most cases, you'd be better off using a Web Application project -
it's a little more work now to get it set up, but you'll be much
happier with the results.

> DBauer.Web.UI.WebControls.DynamicControlsPlaceholder.RestoreChildStructure(­Pair

> persistInfo, Control parent) +255
>
> DBauer.Web.UI.WebControls.DynamicControlsPlaceholder.LoadViewState(Object
> savedState) +209
>    System.Web.UI.Control.LoadViewStateRecursive(Object savedState)
> +251
>    System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList
> childState) +142
>    System.Web.UI.Control.LoadViewStateRecursive(Object savedState)
> +300
>    System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList
> childState) +142
>    System.Web.UI.Control.LoadViewStateRecursive(Object savedState)
> +300
>    System.Web.UI.Page.LoadAllState() +520
>    System.Web.UI.Page.ProcessRequestMain(Boolean
> includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
> +3444
>

> ---------------------------------------------------------------------------­-----

[Andrew Badera]

Did you cut and paste a lot of code into your IDE by any chance? Make sure you aren't accidentally specifying that assembly in the page directive of any of the pages in your solution. With single-page assemblies, each compiled aspx gets associated with a specific assembly, and quite often I've seen people accidentally copy this stuff back into the unpublished, raw code window.

--
--Andy Badera
http://andrew.badera.us/
and...@badera.us
(518) 641-1280
Google me: http://www.google.com/search?q=andrew+badera

[Bruno Colaço]

Hi there!

I'm experiencing the same problem on a development server and have
been googling around for a solution. From the various forums that I
have found discussing the problem (like http://forums.asp.net/t/986130.aspx),
I have reached the following conclusuions:
1. There is no agreement on what causes the error.
2. No provided solution has been referenced for getting the error away
for good.

In my case, the error appeared for the first time after (not
immediately after) a change on an ASCX file. As suggested on some
forums I "touched" the ASCX file to fix the error but it reappeared
after a while.
Another proposed solution to the problem is to clean and rebuild the
whole Visual Studio Solution for every change on the project (even if
it is a simple change on an ASCX file).

I'm trying that right now and will report my results here.

[Andrew Badera]

Clean/Rebuild has not been an effective measure, in my experience.

Either spend hours and hours hunting through code to find a specific fix, or rollback prior to the problem, and eat the merge time. I tend to prefer rollback myself.