ASP.net syntax: Missing entity name

[miksh]

I have "ASP.net syntax: Missing entity name" warning for asp.net controls with an ampersand in the text property but I believe that it's a false yellow alert:
 

<

 

asp:Literal id="lblTitle" runat="server" Text="Schedules & Events" />

 

 

 

 

 

 

[Tsviatko Yovtchev]

Hi Mike,

 Which version of JustCode do you have installed? Can you update to the official release we just published and give that another try?

Sincerely yours,
Tsviatko Yovtchev
the Telerik team

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.

[miksh]

Just installed 2010.1.305.2 - all the same and even more - JustCode report two warning for the same line "ASP.net syntax: Missing entity name" and "HTML: Missing entity name"

Another sad thing is some of my reported bugs & suggestions have not been fixed yet. I don't even see them in your public bug track tool as well:
http://www.telerik.com/community/forums/justcode/code-analysis/quot-missing-quot-in-javascript-minified-files.aspx
http://www.telerik.com/community/forums/justcode/code-analysis/good-code-reg-in-javascript.aspx
http://www.telerik.com/community/forums/justcode/general-discussions/suggestions-for-justcode-error-pane.aspx

[Tsviatko Yovtchev]

Hi Mike,

What you get is a false warning and it's due to be fixed. I am starting an internal issue for it.

In general very few of our issues are public. Most of the cases they are still visible to the person that supplied the initial information about the problem (as will be the case for the issue I am starting now based on you report). So, I can assure you nothing that gets reported goes to the void :) 

However, it's hard to commit on a precise fix date for a given issue.  We are constantly developing new functionality and new issues arise some of which are blocking and require immediate attention. We never give up on fixing a bug, though, so at some point in time everything gets fixed. 

I do realize that the issues you reported are annoying. They are not blocking and not that common, however, and that's why we have postponed them for after the official release. I beg your pardon for the inconvenience caused. Please, stay tuned and try out our subsequent releases.

Regards,
Tsviatko Yovtchev
the Telerik team

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.

[kurt place]

I am still getting this error.  Is this still a false positive or is there a way to 'fix' this?

[Zdravko]

Hello Kurt,

Indeed this warning still exists. We decreased its priority and the fix remained in time and never got to production as it is recommended to always escape such characters.

There are two quick fixes that you can apply in order to get rid of it.
The first one is to ignore it as described here and the second one is to escape the special character. In your case you should replace '&' with '&amp;'

Regards,
Zdravko
Telerik