Why doesn't html.encode return HtmlString

Question

I've been going through and converting my project to use the <%: instead of the <%= syntax, and have been annoyed that I also have to remove Html.Encode(zoozle) all over the place. If it's left in place, zoozle will get double-encoded.

This leaves me wondering, why doesn't Html.Encode return HtmlString, so that it doesn't get encoded again by <%:?

sgriffinusa · Accepted Answer · 2011-01-05 23:22:34Z

1

The HtmlString is a new class introduced in the .NET 4.0 framework. The HtmlEncode method is on the HttpServerUtility class that has been around since .NET 1.1. Microsoft probably didn't change it so as not to break all the previous implementations that rely on this method returning a string. They can't overload it because you can't overload solely on the return type of a method.

Phil Haacked has a regex that can be used to replace all instances of Html.Encode. http://haacked.com/archive/2010/04/29/replacing-html-encode.aspx

answered Jan 5, 2011 at 23:22

sgriffinusa

4,2211 gold badge27 silver badges27 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Why doesn't html.encode return HtmlString

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related