Hi Mike,
I have to strongly disagree with your worries about setting the current
directory. I know this is fixed, but I wanted to explain why I think it is
okay to change that directory. The directory your tests think is the current
directory shouldn't matter, but it is very helpful to be able
Well, not to pick on you Philip, but I would much rather see extra files
left out. In your earlier post you include the bin folder which comprises
most of the size. If you didn't include that, but rather included a simple
build file or instructions or what to put where, then your post would have
Yeah, I had actually thought about checking that
each include resulted in some file being selected. But I think your failonempty
does a pretty good job. It will cover the simple case that you are included
"*.cs" and want something to compile.
I still think we need a feature which lets us
OK, Philip, I'm kicking the tires now. I clicked on the Add button to
add a Hello World C# source file to the list, and now I'm stuck.
What's the next step? (Clicking on Load at this stage throws an
unhandled exception.)
Jeffrey
-Original Message-
From: Philip Nelson [mailto:[EMAIL
I wouldlike to see NAnt run on Mono. Does
anyone want to volunteer to be the point man on this?
For the next majorrelease I'd like to see us
provide a Mono distribution.
--- Scott Hernandez [EMAIL PROTECTED] wrote:
I would like to see NAnt run on Mono. Does anyone want to volunteer to be the
point man on this?
For the next major release I'd like to see us provide a Mono distribution.
What parts of NAnt? I had gotten NAnt.exe to partially run with the last
--- Scott Hernandez [EMAIL PROTECTED] wrote:
Those are good questions.
My goal would be to get things working well enough so that the mono team
feels confident is using NAnt to do their builds.
That at least may be an easier first goal. The MCS task and possibly some
other file utilities?
In an effort to one up people I'm going to try to get nant working under
mono on my iBook (OS X).
My vision is for the core nant distribution to work on any .NET platform
with platform specific tasks in different dll's. I think a global
property should control what compiler the csc task uses.
Okay, we have had this problem come up many times.
The ZipLib produces the incorrect date in zip file (it seems to produce
amodificationDate+ 1 month). This is a problem for us since we use
this library to build our distributions and our nightly builds.
Well, I have update the task to
(from memory) mcs syntax and command line parameters are fairly different than
csc so, if you are a developer familiar with mono, you won't know the correct
syntax for the parameters if they are done in a csc sort of way. Plus, the
compilers don't support exactly the same set of features, so to
(from memory) mcs syntax and command line parameters are fairly different than
csc
For some time now mcs has support for all of the csc options.
Some of the options are no-ops though (like incremental+/-).
Sergey
---
This SF.net email
Philip Nelson wrote:
--- Scott Hernandez [EMAIL PROTECTED] wrote:
I would like to see NAnt run on Mono. Does anyone want to volunteer to be the
point man on this?
For the next major release I'd like to see us provide a Mono distribution.
What parts of NAnt? I had gotten NAnt.exe to partially
I am not sure if this the correct forum, if it isnt them I am sorry but
would appreciate any help.
I am trying to integrate log4Net assembly in the nant-nunit build framework.
The moment I add this line
private static readonly ILog log =
13 matches
Mail list logo
