On the second line, the compiler is complaining about
the fact that I've used an ampersand instead of the
encoding to represent it (which is why the first line
is ok).
<RadioButton Text="{\DlgFont8}I &accept the
terms in the License Agreement" Value="Yes" X="5" Y="0"
Width="250" Height="15" />
<radiobutton text="{\DlgFont8}I &do not accept
the terms in the License Agreement" value="No" x="5" y="20" width="250" height="15"></radiobutton>
The error message given is:
<filepath> ... "fatal error CNDL0031: This is an
unexpected token. The expected token is 'SEMICOLON'."</filepath>
It'd be more helpful to tell the developer what the
compiler means by "This" - it took a few minutes to
realise it wanted the ampersand to be encoded instead
of just its character.
Even better would be to simply not fail? I mean, if it
knows what the problem is, and how to fix it... Make
it a warning, not an error?
Logged In: YES
user_id=991639
Unfortunately, that error comes from the .NET Framework's
XML Validation code. We don't have control over the
messages presented and the Exceptions generated are no
informative enough to do anything about in code.
I wish there was something we could do to improve the
messages but nothing has become obvious.