[niallgc]

Hi,

we've got a step in our build process which checks the value of a macro and either leaves it as it is or sets it to a new value.
The problem occurs in the latest version when the step doesn't seem to be able to interpret the macro properly.

The idea was to check if the macro already contains the
text 'FxCop' and if it does not then this step should be executed.

I've attached a picture of the step settings to achieve this but it ALWAYS built the step.

I've also tried adjusting the condition to check for the macro being defined - if it was then leave it, if not defined then proceed with this step. This also caused the macro to run EVERY time.

Has anybody else noticed a similar bug in the latest version?
(This step was working in earlier versions. Unfortunately I cannot confirm for sure that the latest release introduced the problem.)

Thanks in advance,

Niall