Strange assembly loading error

We have a solution we are in the process of upgrading from .NET 1.1 to
.NET 2.0.  Part of the solution is several projects that contain nUnit
tests.  After the upgrade, all of the test dlls except one work, but one
will not load.  When we try to load it in nUnit, we get this error:

 

 System.IO.FileNotFoundException...

 

Server stack trace: 

   at System.Reflection.Assembly.nLoad(AssemblyName fileName, String
codeBase, Evidence assemblySecurity, Assembly locationHint,
StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean
forIntrospection)

   at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef,
Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean
forIntrospection)

   at System.Reflection.Assembly.InternalLoad(String assemblyString,
Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean
forIntrospection)

   at System.Reflection.Assembly.Load(String assemblyString)

   at System.UnitySerializationHolder.GetRealObject(StreamingContext
context)

   at
System.Runtime.Serialization.ObjectManager.ResolveObjectReference(Object
Holder holder)

   at System.Runtime.Serialization.ObjectManager.DoFixups()

   at
System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(
HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean
isCrossAppDomain, IMethodCallMessage methodCallMessage)

   at
System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deseriali
ze(Stream serializationStream, HeaderHandler handler, Boolean fCheck,
Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)

   at
System.Runtime.Remoting.Channels.CrossAppDomainSerializer.DeserializeObj
ect(MemoryStream stm)

   at
System.Runtime.Remoting.Channels.CrossAppDomainSerializer.DeserializeMes
sageParts(MemoryStream stm)

   at
System.Runtime.Remoting.Messaging.SmuggledMethodReturnMessage.FixupForNe
wAppDomain()

   at
System.Runtime.Remoting.Channels.CrossAppDomainSink.SyncProcessMessage(I
Message reqMsg)

 

Exception rethrown at [0]: 

   at
System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage
reqMsg, IMessage retMsg)

   at
System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&
msgData, Int32 type)

   at NUnit.Core.TestRunner.Load(TestPackage package)

   at NUnit.Util.TestDomain.Load(TestPackage package)

   at NUnit.Util.TestLoader.LoadTest(String testName)

 

 

Trying to debug what might be going on, I turned on fusion logging for
everything, and tried to load it again.  This showed me two entries in
the log.  One where an application called Tests loaded all the test dlls
(including the problematic one) correctly, but another one where
nUnit.exe itself tried to load the problematic dll and failed, but not
any of the other test DLLs.  In the log where it fails, it is trying to
load the test dll from the C:\Program Files\NUnit 2.4.3\bin folder.

 

It makes me think maybe something is just wrong with our project file,
but I am fairly new to nUnit, and can't find anything wrong myself.
Does anyone have any suggestions to help me find the issue?

 

Thanks,

Ian Foutz

Worksoft

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

_______________________________________________
Nunit-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nunit-users