----- 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
