Wierd mixed c++ assembly problem.

  • Thread starter Thread starter Mike Smith
  • Start date Start date
M

Mike Smith

We are having an issue where .NET assemblies are inconsistently being
found/not found. On some runs, everything runs fine. On other runs, we get
exceptions saying that one of our assemblies was not found. Also, if we
were to do a Search using Windows Explorer, sometimes the assembly show up,
and sometimes it doesn't. We inherited this code and the original
developers said the only way they were able to fix the problem was to
reinstall the OS! I don't believe I should have to reinstall the OS, any
other ideas?

Thanks,
Mike
 
Here is the output of the exception.


System.IO.FileNotFoundException: File or assembly name Wrapper, or one of
its dependcies, was not found.
File name: "Wrapper"
at formProj.CDataOperation.Connect()
at formProj.CParaGlobal.ConnectToDataBase()

=== Pre-bind state information ===
LOG: DisplayName = Wrapper, Version=1.0.2606.19210, Culture=neutral,
PublicKeyToken=null (Fully-specified)
LOG: Appbase = c:\BIN\STUDENT\
LOG: Initial PrivatePath = NULL
Calling assembly : formProj, Version=1.0.2606.19445, Culture=neutral,
PublicKeyToken=null
==

LOG: Policy not being applied to reference at this time (private, custom,
partial, or location-based assembly bind).
LOG: Post-policy reference: Wrapper, Version=1.0.2602.19210,
Culture=neutral, PublicKeyToken=null
LOG: Attemping download of new URL file:///c:/BIN/SUDENT/Wrapper.DLL

I've never had to deal with .NET assemblies before, so the above is mostly
greek to me. Also, we can connect to the database through Visual Studio.
We are using VS2003 and Windows 2000 SP4 and .NET 1.1. Some of the machines
had .NET 2.0 installed, but has since been uninstalled because it was
causing issues with some other files. We still get this error regardless if
we execute on a machine that had .NET 2.0 installed, or a machine that has
only every had .NET 1.1. installed.
 
Fixed. It turned out that we needed to install a 3rd party application.
There was a dependency on a DLL that was installed by this third party
application. The only way we found this out was to run depends on the DLL.
To bad the exception didnt point this out earlier it would have saved 5 days
worth of work.
 
Back
Top