, 567 303 601
_
From: Ryan Parlee [mailto:[EMAIL PROTECTED]
Sent: Sunday, February 11, 2007 9:18 PM
To: [EMAIL PROTECTED]
Subject: RE: [nant-dev] solution and compiler arguments
Martin,
I just came across your post about /nowarn /codepage args to csc via nant
However, in double checking this, I found out that the codepage option
is not available in Visual Studio at all, and hence you can't set it
differently for different configurations. So perhaps it's not a
viable option for you, but maybe you can change your codepage in the
enviornment
- Original Message -
From: Martin Aliger [EMAIL PROTECTED]
To: '! nant' [EMAIL PROTECTED]
Sent: Monday, October 25, 2004 11:08 AM
Subject: Re: [nant-dev] solution and compiler arguments
However, in double checking this, I found out that the codepage option
is not available
For now, I'm using modified NAnt version which allow me to specify
additional options. I think it could be useful for others.
If not, I'll
give
up and will try to find another solution (like modify
.csproj for /nowarn
+
setting environment localization for /codepage). But ... I
Hi,
solution configuration=Release outputdir=${output.dir}
projects
include name=*.csproj/
/projects
compilerargs
csc
arg value=/codepage:1250/
/csc
/vbc
arg value=/whatever:option/
/vbc
/compilerargs
/solution
Martin,
I still think that if you need more flexiblity, you should use the
individual compiler tasks.
Why do you need to specifiy additional args in the NAnt solution task that
you don't need when building using VS.NET ?
Gert
- Original Message -
From: Martin Aliger [EMAIL PROTECTED]
... solution is very handy shortcut for this task and
just a little bit is missing...
Martin Aliger
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 30, 2004 5:16 PM
To: Martin Aliger; '! nant'
Subject: Re: [nant-dev] solution and compiler
