Finally, I found out why the <assemblyfolders> are not recognized on one
computer.
My build file looked like this:
<property name="sys.env.TMP"
value="${environment::get-variable('TMP')}"/>
[...]
<target name="build">
<solution configuration="${project.config}"
solutionfile="${project.dir}/${project.name}.sln"
outputdir = "${build.bin.dir}"
>
<assemblyfolders>
<include name="${sys.env.TMP}" />
</assemblyfolders>
</solution>
</target>
On the computer where it did not work, the TMP environment variable was set
to d:\TMP. When I changed it to d:\tmp, the build succeeded. So I think that
NAnt has a problem with a mixed-case path in the <assemblyfolders> tag,
which I consider to be a bug.
On another computer where the build had always succeded, the environment
variable was TMP=C:\TMP\V71.
As a workaround, I now use
<include name="${string::to-lower(sys.env.TMP)}" />
Regards,
Matthias Reuss
on September 29, I wrote:
>
> However, I recently set up a new compile server, and on this
> computer the
> <assemblyfolders> element seems to be ignored. The build
> fails with the
> message "Couldn't find referenced assembly ..." with the
> original Hint Path.
>
> For a test, I copied the third-party assemblies into the
> original Hint Path
> without further installations, and now the build succeeded.
>
> This means to me that NAnt somehow ignored the
> <assemblyfolders> element on
> this computer.
>
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Nant-users mailing list
Nant-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
