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
