--- "Haltunen, Mathew" <[EMAIL PROTECTED]> wrote:
>> Hello all,
>>
>> I've used ant in the past, but now I am using nant to build .NET
>> applications. I am running into a problem handling dependencies.
>> Here's the break down.
>>
>> The dependencies that are handled with the "pre.build" target are built
>> and placed in the directory where this nant script is executed (the
>> .\bin directory). The problem occurs when the "build" target includes
>> the dlls that are created by the "pre.build" target. The name spaces in
>> the "pre.build" dlls are not recognized in the <include> task in the
>> "build" target. Has anyone seen this before? Any help is much
>> appreciated.
>Are the pre.build dlls there when you're done? This is most likely a path
>problem because the fact the pre.build task runs first means that the dlls
>should be there. As a test you could just verify the dlls are there and run
>the main build separately.
Thanks for replying. How do you reply properly anyway?
The “pre.build” target does create the .dlls. However, they are created in the ./bin directory in which the nant command is executed (in this case ADRunner/bin). The dlls are indeed created. If I verify that the dlls exsist and hard code in the path to them, it still fails. That is in the ADRunner/bin directory. I run a sanity check by manually creating the dependent dlls by executing nant in the respective directories. This creates the dlls in PSPerson/bin directory. Pointing the <include> task to PSPerson/bin works fine. It’s the “pre.build? target that creates the dlls in ADRunner/bin/PSPerson.dll that causes a problem. Specifically, the <include> does not seem to work properly.
Thanks again for replying.
Matt
