Formatting bound ASP.NET types requires explicitly changing the HtmlEncode property

DataGridView使用技巧大全

yanchen — Wed, 15 Apr 2009 10:07:04 GMT

收集一些在DataGridVeiw使用技巧，备用。

一、DataGridView单元格验证

1、定义单元格验证要求：验证错误后焦点不离开。实现：单元格的验证可以使用dgv_details_Cel...

re: Formatting bound ASP.NET types requires explicitly changing the HtmlEncode property

guy — Sat, 15 Mar 2008 04:44:19 GMT

This is no longer true. It displays the formatting whether you set it to false or true, but on some workstations it may still show the formatting to be absent. Upload it to the Web and it'll work just fine. I think it's something that got patched in a framework or VS update.

re: Formatting bound ASP.NET types requires explicitly changing the HtmlEncode property

Wayne — Mon, 28 Jan 2008 22:57:40 GMT

I hit this as well, seems pretty silly. thanks for the info!

在GridView中如何格式化Money型字段（downmoon)?

邀月 — Sun, 30 Dec 2007 14:32:57 GMT

在GridView中如何格式化Money型字段（downmoon)?

downmoon — Thu, 01 Nov 2007 04:46:39 GMT

在GridView中如何格式化Money型字段（downmoon)?

re: Formatting bound ASP.NET types requires explicitly changing the HtmlEncode property

Dean — Fri, 12 Jan 2007 01:57:18 GMT

Thanks for this, I was just starting to pull my last few remaining hairs out. What a stupid design flaw!

The fields that I was binding to where double & datetime. How can they be prone to html encoding problems?

re: Formatting bound ASP.NET types requires explicitly changing the HtmlEncode property

Ruben — Thu, 09 Feb 2006 03:32:01 GMT

Also, {0:N} with HtmlEncode off doesn't work for me (Reflector seems to agree on that ;-) At least it's consistent. But unless I'd read your blog, it would have been a loooong search to find the cause of DataFormatString not working. Thanks!

Overriding BoundField.FormatDataValue would be an option, as it's virtual. Hmmm...

re: Formatting bound ASP.NET types requires explicitly changing the HtmlEncode property

Ruben — Thu, 09 Feb 2006 03:20:38 GMT

I think that qualifies as a bug. Or a dumb design flaw. The HtmlEncode should be applied AFTER the DataFormatString. This behavior is just silly and really confusing.

re: Formatting bound ASP.NET types requires explicitly changing the HtmlEncode property

Kevin Daly — Wed, 08 Feb 2006 22:12:49 GMT

That's worth knowing...
Um, I know this isn't the right place, but could I make a suggestion for an enhancement?
Since it doesn't seem reasonable that someone would every explicitly set a format string that they wanted to be ignored, would it be possible to make setting a format string attribute automatically cause an HtmlEncode attribute with value "False" to be added?
Or at least have that behaviour available as a configurable option?

re: Formatting bound ASP.NET types requires explicitly changing the HtmlEncode property

Mads Kristensen — Wed, 08 Feb 2006 20:26:58 GMT

I've experienced the same thing. It makes no sense, since the format string doesn't include any characters that is being htmlencoded. However, if you change your formatstring to {0:N} it will work without htmlencode=false.

----------------------------------------------------
www.madskristensen.dk