Hi,

We have an application that works fine locally but doesn't work when copied to the production server.

Ideas appreciated.

Thanks, Crile

---

Parser Error Message: Could not load file or assembly 'EO.Web' or one of its dependencies. The module was expected to contain an assembly manifest.

Source Error:


Line 2:
Line 3: <%@ Register Src="Publications.ascx" TagName="Publications" TagPrefix="uc1" %>
Line 4: <%@ Register TagPrefix="eo" NameSpace="EO.Web" Assembly="EO.Web" %>
Line 5:
Line 6: <script runat="server">

Thanks, but we are running ASP 2.0 on both servers.

Here's the error detail:

Server Error in '/wheatlandpolice/proof' Application.

---

Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Could not load file or assembly 'EO.Web' or one of its dependencies. The module was expected to contain an assembly manifest.

Source Error:

Line 2:
Line 3: <%@ Register Src="Publications.ascx" TagName="Publications" TagPrefix="uc1" %>
Line 4: <%@ Register TagPrefix="eo" NameSpace="EO.Web" Assembly="EO.Web" %>
Line 5:
Line 6: <script runat="server">


Source File: /wheatlandpolice/proof/MiniPubDownloadLauncher.ascx Line: 4

Assembly Load Trace: The following information can be helpful to determine why the assembly 'EO.Web' 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].

---

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

That solved it - the file transfer was incomplete - thanks.