> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> McKenna, Simon (RGH)
> Sent: dinsdag 22 maart 2005 3:22
> To: 'nant-users@lists.sourceforge.net'
> Subject: RE: [Nant-users] NAnt on Mono on Linux
>
>
> Hello again,
>
> Did more research into
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Ricardo Gladwell
> Sent: maandag 21 maart 2005 16:02
> To: nant-users@lists.sourceforge.net
> Subject: [Nant-users] Potential Bug: NAnt 0.85-rc2 looking in
> non-existant registry setting for Mon
I had this same problem, and found very little information about it via google.
I saw this email from Ioana Goga on this list last November and thought I'd
send a reply.
To embed license info into your assembly, you must first create a .licenses
file from the .licx file. Then you add this .li
Hi All,
I'm posting this here because I'm not sure if this is a bug and I wanted
confirmation before I reported it as such. Please CC replies to my email
address as I'm not subscribed to this mailing list.
The NAnt.exe.config script seems to be looking non-existent registry
setting "SOFTWARE\No
Hello again,
Did more research into the problem, findings below:
-> Are you indeed running NAnt on Mono SVN HEAD ?
The build was from SVN head as of last Sunday.
mono -V reports:
Mono JIT compiler version 1.1.5, (C) 2002-2005 Novell, Inc and
Contributors. www.mono-project.com
TLS:
> The point is that you can't nest ${...} properties but you CAN still
> concatonate strings in expressions, so '.\${src.dir}' becomes '.\$' +
> src.dir
Actually, '.\${src.dir}' becomes '.\' + src.dir... the backslash here
is a directory separator, not an escape character.
-T
-
Sorry for the belated response, but I just figured out an
alternate syntax to do what you are trying to do, and thought other people might
find it helpfull:
The point is that you can't nest ${...} properties but you
CAN still concatonate strings in expressions, so '.\${src.dir}' becom
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> [EMAIL PROTECTED]
> Sent: maandag 21 maart 2005 21:07
> To: [EMAIL PROTECTED]; nant-users@lists.sourceforge.net
> Subject: RE: [Nant-users] MailLogger e-mails have wrong
> encoding in Outlook
>
Title: Looking for a Temporary Consulting Nant Developer in Dallas
To whom it may concern,
I am currently looking for a temporary consulting NAnt Developer in the Dallas area to help with NAnt implementation.
Please let me know if this is the correct forum to post this type of request, or
Gert wrote:
> However, I just added a new property (called MailLogger.body.encoding)
that allows you to configure the encoding of the body of the message
(just in case you need it).
Thanks Gert, envious that it works for you! It could well be something
about how they configure the machines here at
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> [EMAIL PROTECTED]
> Sent: maandag 21 maart 2005 19:53
> To: nant-users@lists.sourceforge.net
> Subject: [Nant-users] MailLogger e-mails have wrong encoding
> in Outlook
>
> We have our build scr
We have our build scripts set up to send the output of the build to us
on failure - no problem there. The issue is the "encoding" that
Microsoft Outlook chooses to apply when receiving one of these e-mails -
it applies "Western European (ISO)", which in turn means that it misses
the carriage return
I'm trying to use the solution task in 85-rc2 (as well as the nightly)
to build our solution. Our code is a complicated mix of straight
legacy C, along with C++, and C#. When I try to build the solution,
I get a C1192 fatal building a managed C++ projects that depends on C
projects and C# projec
Paul,
I
think that issue is fixed in the latest build of NantContrib 0.85.
Can you try that?
Felice
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf Of Paul
CowanSent: Monday, March 21, 2005 9:02 AMTo:
nant-users@lists.sourceforge.netSu
Hi all,
I am getting the following error when I try to add files to a
sourcesafe project:
BUILD FAILED
C:\Inetpub\wwwroot\NAnt\bin\vor_test.build(20,4):
Failure adding 'C:\Inetpub\wwwroot\NAnt\NAnt.aspx' to
SourceSafe.
Invalid OLEVERB structure
Total time: 0.7 seconds.
Paul,
you're checking out your code to C:\Inetpub\wwwroot\NAnt, I assume
this is not the same place you are running your build from?
If not, try adding a "basedir" attribute to your sources and resources
elements...
You could then pull the path out into a property to redu
Hi all,
I’m trying and failing to get to grips with NAnt.
I can successfully get all the required files from sourcesafe, using the build
file below, but the CSharp compiler is complaining:
[vssget] Getting '$/vor/build/test' to
'C:\Inetpub\wwwroot\NAnt'...
C:\Inetpub\wwwroo
17 matches
Mail list logo