- Original Message -
From: "Douglas R. Steen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 03, 2003 6:57 AM
Subject: [Nant-users] Specifying -logger in the build file
> I'm using the -logger:NAnt.Core.MailLogger commandline option so that
> I'll get an email with
Douglas,
you can log to a default text log, and then write a target that will send
email to you.
For example:
I have some ant build scripts that I want to translate to nant, do you know
of any tool(s) out there that would make my job easier?
Thanks in advance,
Rodrigo
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net
MS Build was presented at the PDC and there's alot of stuff on the web if you
search in Goolge for MSBuild. I've read a few blogs where MS guys are saying
that Ant / NAnt is the inspiration, but that they're having to roll their own
due to licence issues with the opensource projects. I get the impr
Dianna,
I have read a lot of talk about MSBuild here before, and none of it has
given me the impression that MSBuild will "bash the foundation of NAnt."
In fact, I think that the two environments will complement each other
very well. Both will have very similar features. And they may be able to
wo
First, I must admit that being a *Windows Developer* has been good to me and
my family for all these years. So, I've always try to look at things from
all point of view and try carefully not to *bash* or *judge* MS blindly.
But, this is a *bit* too much.
I think MS should at least *thanks* the de
Title: Using the License tag
I have a 3rd party control that I'm trying to create a buildfile for. I have found the license tag, but have no idea where to actually put it in the "build" process! Before the csc tag, as an argument to the csc tag...??? Any help in getting this to its correct
Hi,
* Block, Jeffrey A. (Jeff) wrote on 03.12.2003 (14:10):
> process! Before the csc tag, as an argument to the csc tag...??? Any help in
Before the csc task. It generates a license file which then
must be included as a resource in the csc task.
-sa
--
sa at programmers-world dot com
http://
Title: RE:Editing .build files w/syntax hilighting in VS.NET
I've read through the archives and followed previous advice regarding how to get .build files fully recognized by VS.NET with Intellisense/validation. I've configured it such that VS.NET recognizes .build files as XML, and the opened
I'm also having similar problems with nant schema. I couldn't get it to work
using the method you described.
There's a workaround: if you add the schema to the same project (maybe just
the same solution - I don't remember) as your build files - the intellisense
works (more or less - the schema is n
First off let me say I agree
with the point of this post. I mention in my Open Source .Net book MS should
thank the Apache Ant developers who had a really cool idea. But I can
understand MS wanting to fully control such a critical part of their product.
As I mention on my blog
(http:
Title: Validation of build files in VS.NET
Hi
Gerrod,
Save
the XSD from the webpage into this folder:
C:\Program Files\Microsoft Visual Studio .NET
2003\Common7\Packages\schemas\xml
This
is the secret place where VS.NET looks for schemas.
Then
open an XML file in the VS editor, and c
Title: RE:Editing .build files w/syntax hilighting in VS.NET
Line 3 should say something like that: http://nant.sf.net/schema/nant-20030903.xzd
Thanks,
Oleg
From: White, Jeffrey
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 03, 2003
1:04 PM
To: '[EMAIL PROTECTED]'
Subject:
Title: Message
Let me start this by saying "I'm sorry if you thought
I was bashing".
It was a poor attempt at humor :)
I live and breath the MS theme. I have drank the cool
aide years ago.
Your comments Daniel are most excellent. The contributors should all be proud that MS
would take notic
I just wish the (Xml Schema) noNamespaceSchemaLocation hint was honored in
the editor. :) Oh, that would make it so easy...
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xmlsdk/htm/xsd_ref_7ld1.asp
BTW. The NAnt schema file generated by the task doesn't create
array and colle
In the next nightly build there will be a new target called "deploy-schema"
that will copy the schema file to the vs.net (7.0 and 7.1) schema
directories. That should help a little :)
Please note that the targetNamespace is in the form of
"http://nant.sf.net/schemas/${project.name}-${project.vers
16 matches
Mail list logo
