We had seen a similar problem where the object being tested threw a custom exception defined in another assembly, and NUnit had problems loading the exception's assembly. It turned out that even though NUnit said that it couldn't load the exception's assembly, the real problem was that NUnitCore.dll wasn't in the path. The problem was fixed when the developer copied nunitcore.dll into the same directory as the other files. So it might be something worth trying to copy all your dlls into the same directory along with NUnitCore (or copy everything to program files\nunit\bin) and see if it works then. There's a bug report [1] on sourceforge that seems related.
[1] http://sourceforge.net/tracker/index.php?func=detail&aid=505054&group_id=10749&atid=110749 -----Original Message----- [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] wrote: > However, when the test case is invoked, it fails in > BeginInvoke() because the type TestDelegate() cannot be > loaded!!! Obviously, everything works just fine if the code > is not invoked from NUnit. Is the assembly that TestDelegate the same assembly that the TestCase lives in? If not is the TestDelegates assembly available on the path so that the loader can find it? Later, Drew You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
