Noobie Error?

microsoft.public.dotnet.framework

14 Jun 2006 12:21 PM

Coness

I've created a simple asp.net page which basically takes in a cookie
from a classic asp, and uses that cookie to retrieve session
information from a SQL Server Table. I grab the session information
using a COM object (dll) that I wrote. All works perfectly on my
development box, but when I implement into production I get the
following error:

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: The specified
module could not be found.

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.

Stack Trace:

[FileNotFoundException: The specified module could not be found.]
   Session.__login.Page_Load(Object sender, EventArgs e) +13
   System.Web.UI.Control.OnLoad(EventArgs e) +67
   System.Web.UI.Control.LoadRecursive() +35
   System.Web.UI.Page.ProcessRequestMain() +750

Coming from the classic world, I would be able to troubleshoot this
with no problems, but I just don't understand what this message means.
My IDE of choice is VS 2003. Both boxes are running IIS6 and .Net
Framework (1.1). The asp.net app is put in a sub virtual directory in
the main web directory (e.g., /maindirectory/asp.net app).

I am implementing the application via VS.Net Web Setup Project (e.g.,
myapp.msi). We have multiple web sites on the production box, so when
I install myapp.msi, it seems to want to install it on the wrong web
site. I basically cut and paste it into the correct website. I don't
believe this causes the issue as it should be the same as XCopy. Any
help would be appreciated. Deploying should be as easy as creating a
bin directory and copying files over right? If someone could: (1)
clerify deployment of an asp.net application into an existing classic
asp site that would help me greatly. (2) help me w/ this error.

TIA!