If I start my unit tests from TestDriven.NET under VS2008, they run pretty much immediately.
If I start my unit tests using nunit-console.exe, the NUnit console hangs for five minutes before actually running my tests. If I attach a debugger, it seems to be spending its time in System.IO.MemoryStream.Read, called from System.Runtime.Serialization.Formatters, called from System.Runtime.Remoting, on the other side of some native-managed transitions called by NUnit.Core.ProxyTestRunner.Test.get. Sometimes, it's in System.Runtime.Serialization.ObjectManager.RecordFixup or .FindObjectHolder.
This is with NUnit-2.5.2 on 32-bit XP, fully patched. All assemblies are targeted to .NET 2.0.
What is nunit-console up to? Is there any way to persuade it to not do it?