But, except for that one string entity referenced, there's nothing to say this is HTML encoding. I bet it's UTF8 vs ASCII, not HTML entities. If it were HTML encoding, then the OP's original effort would have, if clunky, worked, right?
∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Thu, Sep 10, 2009 at 3:56 PM, Cerebrus <[email protected]> wrote: > > I did too... until I decided to create an EncodingUtility class for > these purposes. ;-) > > On Sep 10, 9:33 pm, Brett Allen <[email protected]> wrote: >> Just because it isn't a web application does not mean you can not add >> a reference to System.Web to use the HttpUtility class. >> >> I've done this in several windows forms applications that must >> interact with websites and deal with Html encoding/decoding. >> >
