Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / General / February 2006

Tip: Looking for answers? Try searching our database.

Control properties with entity references declared in ASPX get converted to character values

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
jesl@lundbeck.com - 13 Feb 2006 18:51 GMT
Group,

I have created a User Control with the property "Html" of type string.
If I declare this control on an ASPX page with the value "<b>This is an
entity: &lt;</b>" for the property "Html", the ASP.NET parser seems to
automatically convert the entity reference "&lt;" to it's corresponding
character value "<".

For example, if the tagprefix and tagname for the user control is "dn"
and "test":

<dn:test Html="<b>This is an entity: &lt;</b>" id="test" runat="server"
/>

... this will result in a "Html" value of:

"<b>This is an entity: <</b>"

Why does this happen? It is quite annoying because I need to preserve
the entity reference. Is there any way to preserve entity references in
properties of type string when these are specified declaratively?

Thank you!
DWS - 14 Feb 2006 16:52 GMT
Jesl,
Take a look at the httpserverutility methods.  htmlencode and htmldecode.
These two methods change string to from &lt to < etc.

http://msdn2.microsoft.com/en-us/library/system.web.httpserverutility_members.aspx

Good Luck
DWS

> Group,
>
[quoted text clipped - 19 lines]
>
> Thank you!
jesl@lundbeck.com - 15 Feb 2006 08:31 GMT
Thank you, but the problem is that the entity refrences get converted
even before I can get hold of the string value. Remember: I am reading
a string property set declaratively in the ASPX. I suspect that the
problem is that it is the default TypeConverter for strings in the
ASP.NET framework that is the culprit. Any thoughts on that or how to
write an alternative TypeConverter that does not touch the string?

/jesper

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.