A name was started with an invalid character.??

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

When I try to select one of the following enums, I see "A name was started
with an invalid character." in the tooltip (Intellisence) and under the
Summary heading (object browser). Other enums seem to behave normally. I
even removed the <remarks/> comment with no change in behavior.

When I build I see the following warning for each enum value:
warning CS1570: XML comment on
'CreditorMigration.SourceAndDestination.PayerToUs' has badly formed XML -- 'A
name was started with an invalid character.

What gives? Should I just ignore it?

**tabs removed**
********************************************
/// <summary>
/// The possible Fee Sources and Destinations
/// </summary>
public enum SourceAndDestination
{
/// <summary>
/// Fee collected by Us directly from the Payer
/// </summary>
/// <remarks>WHEN (cpd.CustPaysFee = 1 AND cft.FeeData <> '0')</remarks>
PayerToUs,
/// <summary>
/// Fee collected by Us and rebated back to Biller
/// </summary><remarks>WHEN (cft.MktFeeData <> '0')</remarks>
UsToBiller,
/// <summary>
/// Fee collected by Us from the Biller
/// </summary><remarks>WHEN (ISNULL(cpd.CustPaysFee, 0) = 0 AND
cft.MktFeeData <> '0')</remarks>
BillerToUs
}

********************************************
 
Nevermind... problem solved. The <> within the <remarks> section was
confusing VS. I did remove them but I didn't actually save the file.

How does one embedd brackets within comments?
 
It might be your <> (not equal to) opperator in the remarks, though you
said it works fine elsewhere...

Not quite sure why it would barf like that, at least not right off-hand.
 
You can replace that with the entity reference, ampersand + lt,
amersand + gt

See MSDN's XML Documents [MS XML] character and entity reference page.
 
kevin said:
When I try to select one of the following enums, I see "A name was started
with an invalid character." in the tooltip (Intellisence) and under the
Summary heading (object browser). Other enums seem to behave normally. I
even removed the <remarks/> comment with no change in behavior.

When I build I see the following warning for each enum value:
warning CS1570: XML comment on
'CreditorMigration.SourceAndDestination.PayerToUs' has badly formed XML -- 'A
name was started with an invalid character.

What gives? Should I just ignore it?
Click to expand...

No - use &lt;&gt; instead of <> - currently it thinks you've got a tag
with no name.
 
Back
Top