> 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
