Hi,
>I have different cases : Strings, BOOL, etc...and in these cases
>the same problem occurs.
yes, this is by design. In Visual Studio 2003, the [!if xxxx] should be
applied to the case of checking the specific control option, if you want to
check a symbol's value(e.g. string, bool, ...), then you need to use the
[!if xxxx != 0] syntax, please refer to the sample code of the following
MSDN article:
Template Directives
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore/html
/vcoriTemplateDirectives.asp
Thanks!
Best regards,
Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn
This posting is provided "AS IS" with no warranties, and confers no rights.
F.P. - 12 Jan 2006 20:55 GMT
Hi,
Thanks for your answer. I
think it could be interesting to update the web-page with the comments you
sent me. I mean by making clearly the distinction you have described Control
/ Value :
"the [!if xxxx] should be applied to the case of checking the specific
control option, if you want to check a symbol's value(e.g. string, bool,
...), then you need to use the [!if xxxx != 0] syntax"
Thanks,
F.P.
> Hi,
>
[quoted text clipped - 26 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
"Gary Chang[MSFT]" - 13 Jan 2006 02:10 GMT
yes, I agree with you, I will ping the corresponding product team about
this problem, thanks for your understanding!
Good Luck!
Best regards,
Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn
This posting is provided "AS IS" with no warranties, and confers no rights.