Fixing a Date Formatting Bug in ASP.NET 2.0

Sometime between beta 2 and beta 3, a bug crept into ASP.NET 2.0's BoundField class that prevents date formatting from working. In the following declaration, the “{0:d”} is ignored:

The bug was slated to be fixed in the RTM release, but alas, it wasn't. There is, however, a work-around: set the BoundField's HtmlEncode property to false:

<asp:BoundField HtmlEncode="false" ... />

Microsoft is aware of the bug and has promised that it will be fixed in a future release.

On Nov 17 2005 7:20 AMBy jprosise
With 5 Comments Jeff Prosise

Comments (5)

  1. Joe Antonaccio

    HtmlEncoding=&quot;false&quot; does not work, the server does not recognize this property (attribute)... at least my server doesn't

  2. Spencer

    HtmlEncoding=&quot;false&quot; should read HtmlEncode=&quot;false&quot;. This bug applies to currency {0:c}. Just add the code above to make it work

  3. Jeff Prosise

    My mistake; the correct property name is HtmlEncode, not HtmlEncoding. It's fixed now. Thanks for the catch!

  4. Michel

    Hello, i have the same problem but it's not in the formview and i don't have the property HtmlEncode. Do you have any idee ? Thanks, Take care Michel

Leave a Comment

Archives

Tags