Re: [nant-dev] solution and compiler arguments
Hi Ryan, yes - I implemented it locally in my patched version. It never propagate to main revisions though. In last versions there is proposal for CustomProperties, an array of arbitrary properties, which .net 1.1 builder could use as /nowarn and /codepage values. I think, this will be quite nice implementation. Other builders (like msbuild ala net 2.0) could use it the other way, though! Ing. Martin mailto:[EMAIL PROTECTED] Aliger http://www.gordic.cz/ http://www.gordic.cz/ GORDIC spol. s r.o. GORDIC spol. s. r.o., Erbenova 4, 586 01 JIHLAVA Tel: 567 309 136, 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. http://www.mail-archive.com/nant-developers@lists.sourceforge.net/msg04885.h tml Did you ever implement this nant extension? I am in the same situation and would like to be able to specify these settings via nant rather than update several csproj files. Thanks, Ryan gordic.gif Description: GIF image - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] solution and compiler arguments
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 rather than passing it to the compiler? 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 don't like workarounds as permanent solution. VS normally has two configurations (Release and Debug), but you can create as many as you want. Each configuration corresponds to one specific set of properties, which in turn map to various command line operations. It's easier to see this for C++ projects, because if you check the properties page for a C++ project, one of the tabs shows the command line it generates. But it's the same principle for C#, e.g. there's a property tab for setting the suppression of specific warnings. This can be used, for example, to have both an optimized and unoptimized release build, or perhaps to build a trial version with different settings than the ones people pay for. Yes - in the C++ project it is well done. Perhaps new C# project in VS2005 will be simmilary powerful (even that I still doubt about msbuild vs nant) Martin --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] solution and compiler arguments
- 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 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 rather than passing it to the compiler? 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 don't like workarounds as permanent solution. I'm not totally against this, but I want to avoid running into issues with this once we switch to using the NAnt compiler tasks (in the solution task). Also, users that want complete control could ofcourse use the individual compiler tasks instead. Gert --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] solution and compiler arguments
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 don't like workarounds as permanent solution. I'm not totally against this, but I want to avoid running into issues with this once we switch to using the NAnt compiler tasks (in the solution task). Sure. I think we should do this move soon (just after release). Those compilerargs could perhaps wait till moving. Also, users that want complete control could ofcourse use the individual compiler tasks instead. Agree. Martin --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] solution and compiler arguments
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
Does anyone like this? I really need that /codepage switch to csc (called
via solution task). I'm willing to code this (or change mine implementation
to be acceptable to community). I think this is usable addition - not
limited just for mine needs.
Martin
btw: does anyone know, if there is some switch or registry entry to convince
VS2003 to create all new files at specific encoding? For us in Czech it is
created in the 1250 code page by default. I know how to save one file in
other encoding (File/Advanced save options) but new files are still in the
1250 :-/
btw2: /nowarn is no problem since I modify .csprojs and add /nowarn there.
but /codepage coudn't be specified this way.
---
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] solution and compiler arguments
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]
To: '! nant' [EMAIL PROTECTED]
Sent: Thursday, September 30, 2004 5:07 PM
Subject: [nant-dev] solution and compiler arguments
Hello,
I just tried to migrate to newest nightly of NAnt and found (again) that
I
have to specify some custom options to csc.exe when compiling mine
projects:
solution configuration=Release outputdir=${output.dir}
includevsfolders=false
projects
include name=*.csproj/
/projects
compilerargs
arg value=/codepage:1250/
arg value=/nowarn:0612/
arg value=/nowarn:0618/
arg value=/nowarn:1591/
arg value=/warnaserror/
/compilerargs
/solution
I remeber there was serious complains against this patch of mine. Maily
because arguments are compiler and language specific. What about to
restructure it somehow to be acceptable by community? E.g.
compilerargs
csc
arg value=/codepage:1250/
/csc
/vbc
arg value=/whatever:option/
/vbc
/compilerargs
Martin
---
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] solution and compiler arguments
Why do you need to specifiy additional args in the NAnt
solution task that you don't need when building using VS.NET ?
I have to specify /codepage parameter because our build server is English
Win2003 Server but most of desktops have Czech localization. Bad thing is
that .csproj and .cs files are at 'Windows 1250' encoding what is default in
the czech windows (so it compile at desktops) but it is not default code
page on English windows (produce compile errors)...
I know - I could reencode all .cs and .csprojs into utf-8 and those
difficulties disappears. Unfortunatelly this is not acceptable solution in
our environment. Moreover I cannot force all developers to reconfigure
theirs Visual Studios.
Next I want to specify some
arg value=/nowarn:0618/
becouse I want some warnings (like missing XML comment) not to fail build.
Again - it is HARD to force all developers (several tens) to configure all
theirs .csprojs correctly. What I want to do is to _force_ build process to
use some common environment.
For this I could modify .csproj so I _should_ be able to do it even with no
support from NAnt. But I dont see any way in case of /codepage.
I still think that if you need more flexiblity, you should
use the individual compiler tasks.
Maybe I could. But it is realy hard when you have several hundereds of
.csprojs. Of course - I could write mine own .csproj parser and create
.build script from it then nant this script. But I do not see much sanity
in such resolution... 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 arguments
Martin,
I still think that if you need more flexiblity, you should
use the individual compiler tasks.
Gert
- Original Message -
From: Martin Aliger [EMAIL PROTECTED]
To: '! nant' [EMAIL PROTECTED]
Sent: Thursday, September 30, 2004 5:07 PM
Subject: [nant-dev] solution and compiler arguments
Hello,
I just tried to migrate to newest nightly of NAnt and found
(again) that
I
have to specify some custom options to csc.exe when compiling mine
projects:
solution configuration=Release outputdir=${output.dir}
includevsfolders=false
projects
include name=*.csproj/
/projects
compilerargs
arg value=/codepage:1250/
arg value=/nowarn:0612/
arg value=/nowarn:0618/
arg value=/nowarn:1591/
arg value=/warnaserror/
/compilerargs
/solution
I remeber there was serious complains against this patch of
mine. Maily
because arguments are compiler and language specific. What about to
restructure it somehow to be acceptable by community? E.g.
compilerargs
csc
arg value=/codepage:1250/
/csc
/vbc
arg value=/whatever:option/
/vbc
/compilerargs
Martin
---
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
