I havent tried the .dll.config to be honest.. i read the documentation and expected it to work the way it explains.. the other solution is not really acceptable ..
I tried running nunit-console.exe Main.unit and it writes: ProcessModel: Default DomainUsage: Default Execution Runtime: Default I'm assuming some of those should change if it registered my config file? ok, just tested it out of curiosity.. and it does register in the output.. adding a x.tests.dll.config and running nunit-console.exe on it produced this: ProcessModel: Default DomainUsage: Single Execution Runtime: Default I'm not sure how to confirm the ThreadPriority though.. i'm not sure right clicking the nunit-console.exe in the taskmanager is the right way to go.. because it's still normal there :) Glad we're getting closer to a solution! -- Config documentation inaccurate or functionality non-existent https://bugs.launchpad.net/bugs/659969 You received this bug notification because you are a member of NUnit Developers, which is subscribed to NUnit V2. Status in NUnit V2 Test Framework: New Bug description: this page: http://nunit.org/index.php?p=configFiles&r=2.5.7 describes how placing a config file with certain parameters can change the behaviour of running nunit.. Now if only any of them worked.. _______________________________________________ Mailing list: https://launchpad.net/~nunit-core Post to : nunit-core@lists.launchpad.net Unsubscribe : https://launchpad.net/~nunit-core More help : https://help.launchpad.net/ListHelp
