> 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
