I'm slightly confused (it doesn't take much!). Which tasks have been
modified? I raised the same problem last week (see "Problem with vbc task"
post) and Gert kindly provided the response that VS tries the path to the
Key file first from the current directory, and if it can't find it there,
then
Garth,
This should indeed be fixed in cvs now. But ofcourse, first test it before
changing your complete build process.
Let me know if you encounter any issues.
Gert
- Original Message -
From: "Garth Ormsby" <[EMAIL PROTECTED]>
To: "Nant Users" <[EMAIL PROTECTED]>
Sent: Monday, March 2
When I try to build NAnt from the Makefile, it usually hangs
on one of the csc task targets. It does not always hang on the same target, and
if I keep trying “make” the build sometimes eventually completes.
I am running on a Dell Precision 530 with RedHat 9 and Mono
0.31.
The Dell
Hi all,
Firstly, quick thanks to the team for a great tool and responsive mailing
list! Our entire dev + build process is slowly being built around nant (+
nunit/asp, ndoc etc), and that decision was much easier to make given the
activity and responsiveness on the list.
Double-check: does this m
I decided to implement option 1.
This is now in cvs.
Gert
- Original Message -
From: "Gert Driesen" <[EMAIL PROTECTED]>
To: "Ian MacLean" <[EMAIL PROTECTED]>; "Eric Fetzer"
<[EMAIL PROTECTED]>
Cc: "Florian Benischke" <[EMAIL PROTECTED]>; "Nant Users"
<[EMAIL PROTECTED]>
Sent: Sunday, Ma
I looked into this, and apparently VS.NET runs csc with \obj\ as working directory or output directory (the
compiler look in both the current directory and the output directory for
locating the key file). I think it might actually use \obj\ as output directory, and then copy the
assemblies to the
