From: Darren S. <dsy...@op...> - 2003-05-29 13:11:44
|
I've recently upgraded to NAnt 0.8.2 and have seen a change in behaviour with the nunit2 task. My build file contains: <target name=3D"common-test"> <nunit2 basedir=3D"${nant.project.basedir}"> <test assemblyname=3D"${nant.project.basedir}/${build.dir}/${component-filename= }" type=3D"Plain" fork=3D"true" /> </nunit2> </target> The component assembly being tested has an app.config file which also specifies an additional probe path for dependent assemblies: <runtime>=20 <assemblyBinding xmlns=3D"urn:schemas-microsoft-com:asm.v1">=20 <probing privatePath=3D"deps;"/>=20 </assemblyBinding>=20 </runtime>=20 =20 When nunit2 runs the tests within the component assembly it complains = that it can't find the dependent assemblies (which are to be found under the = deps subdirectory). Doesn't nunit2 support private probe paths in the app.config? Using the NUnit GUI the tests run fine. I've tried last night's snapshot (0.8.3 ?) and this exhibits the same behaviour. Darren Syzling mailto:dsy...@op... ------------------------------------------- This message may contain information which is confidential or = privileged. If you are not the intended recipient, please advise the sender = immediately by reply e-mail and delete this message and any attachments without retaining a copy.=20 |