Here's the reply I got from one of the VCBuild developers, when I asked him how to suppress warnings using VCBuild.
not as such, no. you need to pass the switches to the compiler (/WX) and tools, not vcbuild.
you could however create a property sheet that sets the switches and use "vcbuild /override:<propsheet>", which would get you the same effect as having a switch on vcbuild...
What type of warnings are you seeing from the VCBuild task
You mentioned in your earlier post that you are using Beta2. There have been a lot of changes since Beta2 - especially around the VCBuild/MSBuild integration story, so if you are using the VCBuild task, you will certainly want to get a later relese - preferably the Release Candidate.
I use the /override:<path> command-line switch and the <VCBuild Override=""/> attribute in an MSBuild project but they don't work unless the .vcproj file actually references the file, so it doesn't really help me to have overrides for different projects built in MSBuild. Am I missing something I have to do in order to not specify anything in the .vcproj and use .vsprops files
VCBuild Task and Warnings
robbyduffy
Here's the reply I got from one of the VCBuild developers, when I asked him how to suppress warnings using VCBuild.
not as such, no. you need to pass the switches to the compiler (/WX) and tools, not vcbuild.
you could however create a property sheet that sets the switches and use "vcbuild /override:<propsheet>", which would get you the same effect as having a switch on vcbuild...
--Rajeev
Ben Kitzelman
Dan
angelLee
What type of warnings are you seeing from the VCBuild task
You mentioned in your earlier post that you are using Beta2. There have been a lot of changes since Beta2 - especially around the VCBuild/MSBuild integration story, so if you are using the VCBuild task, you will certainly want to get a later relese - preferably the Release Candidate.
Thanks.
Faisal Mohamood
IrvineLewis