I just wanted to document the experience I had with nant on my linux box. In
the end it was a partial success but there were a few things I didn't figure
out right away and it may be good to have them documented here.
Day one, load linux in a dual boot with Windows 2003. My previous install
--- Scott Hernandez [EMAIL PROTECTED] wrote:
The projecthelp uses xsl templates to transform the source document (build
file) without doing any includes (or actually running any tasks; like
property/). This makes it pretty useless in many cases.
At this point I think we need to re-write
--- Damir Simunic [EMAIL PROTECTED] wrote:
Since there is so much interest in this msbuild thing, here's the list of
namespaces Microsoft.Build.BuildEngine
The book they handed out with the PDC alpha bits, Introducing Longhorn for
Developers, Brent Rector, Microsoft Press, has a fairly
Well, to be honest : I don't have a clue ... That's perhaps why we're still
stuck with the GPL license :-)
I am pretty sure the copyright holder can do whatever they want, so long as
they aren't bound to the gpl by other source code or libraries in the
application. NAnt may be bound to the
Reason: One of the most common complaints I hear about NAnt is that its
too hard to use, even though it oozes power and flexibility. A lot of
people run with Visual Build from Kinook (another fine product), but I
think some kind of designer support would give NAnt the edge.
Yeah, Alex Lowe
That's what it looked like but I wanted to make sure that it wasn't just
unfinished business. I'll proceed with the idea or working from the xml
directly, thanks.
--- Ian MacLean [EMAIL PROTECTED] wrote:
Philip,
the Nant project class and others are not designed to be DOM like. Many
elements
--- 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
I'll offer one counter point of view to using NAnt from COM. I had started,
but lost the motivation to complete, a task to have NAnt tasks callable from a
DTS package. It's entirely possible that building this functionality would
require no COM visibility, ie the implementation just has the name
while in fact we could add more infomation to that error message by adding
the Message of the innerexception, eg.
you bet!
---
This SF.net email is sponsored by: ValueWeb:
Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
No
Can you run the NUnit gui correctly? Is it installed under Program Files or
somewhere else? Have you tried setting the assembly reference in your test
project to the assembly in the NAnt/bin directory?
It almost has to be mismatched dlls.
--- Anthony Francisco [EMAIL PROTECTED] wrote:
--- Ian MacLean [EMAIL PROTECTED] wrote:
I've created a new NAnt.Win32Tasks assembly to hold win32 specific
stuff. I've moved those tasks that fail to compile on linux in there to
start with so that I can move forward with getting NAnt building on with
mono/linux. Obviously compile on
(BTW, was curious if any NAntians are using #Develop rather than Studio
to work on NAnt. Anyone?)
I use it when I work at home but aren't booted in linux where I use gvim ;-)
---
This SF.net email is sponsored by: Tablet PC.
Does your
Actually, nothing to report with Nant except that the tedious process of
building the gnome libraries and all supporting packages on my older suse linux
system, did finally get me to the point of running a gui debugger on NAnt. And
the result? I stepped into an infinite loop. Same thing with
What seems to happen is that the top level directory is ignored or
identified as an invalid URI if I attempt to compile my sources from the
same directory as my build file. I have the following code:
sources basedir=
includes name=**/*.cs/
/sources
A basedir of
Then, get rid of any classes
that have using Win32 in them.
Unfortunately I just added using Win32 to project.cs to support the
multiple runtimes. I want to come up with a way to partition
this so that the registry access stuff is skipped on a non-windows
build. Maybe thru use of #ifdef.
propertyexists is false when the property does NOT exist OR the property is
false
sounds dangerous to me. Some operation x is supposed run or not, presumably
based on a carefully considered condition. If I forget to set it, I may get
unexpected results.
And Philip... I'm curious as to the environment you got mono NAnt to run
in. Cygwin, or the real deal in linux?
Suse Linux 8.0, shell script for the initial build, GVim text editor
---
This sf.net email is sponsored by:ThinkGeek
Welcome to
--- Ian MacLean [EMAIL PROTECTED] wrote:
Which is why the mcs task should go and we use the same csc task for
both. The stuff i'm working on with loading settings from the confiog
will allow this. Ie if you set the current runtime to be mono - it will
know to call mcs.exe instead of csc.exe
Trying to compile nant under mono. What I originally thought was an xml short
fall is actually a reflection shortfall:
element has more than one match for attribute_type
Anyway, the problem occurs trying to compile McsTask (and other times using
Mono with .net compiled assemblies). McsTask
hmm - well that registry code will be removed shortly. Its just to get
the SDKFramework path I think.
exactly.
Can I assume that the registry won't be supported under
Mono?
I would have thought not. Considering its in the Microsoft.Win32
namespace. And it definately won't be
A few people wrote about a bug that happens if you load a project without first
selecting a build file. Thanks! This version just dims the load button until a
file is selected. Amazing I never did that in over 8 months of use ;-)
I included only the .exe and source. To use, you will have to
--- Brian Deacon [EMAIL PROTECTED] wrote:
Just wanted to pipe up and say that I personally am really interested in
hearing any gotchas and resolutions in getting nant and mono to play
nice with each other. So thanks, Philip.
Yeah, I had pretty much set aside my interest in Mono until NAnt
--- 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?
(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
I have a fairly low tech, but useful winforms app I wrote that I would like to
contribute to the project. It's a gui for NAnt, but unlike the nant gui for
vs-studio, this is an alternative to the command line for NAnt build files. I
call it NAnt Explorer and here are it's features (and not much
26 matches
Mail list logo
