Tags
#sp #SP2010NL 3D AJAX ASP.Net CAML Cloud CodePlex CSS Document Sets Dynamics CRM FAST 2010 Forms Based Authentication InfoPath JavaScript jQuery Managed Metadata MOSS Object Model Search SharePoint Designer 2010 SharePoint Profile System Silverlight soccerino SP2010 Visual Studio 2010 Word Automation Workflow XSLTArchives
-
RSS Links
Tweets
- #ttpi uitje was super. achter een boot gehangen, Kubb, bbq en Paco op de trampoline: http://yfrog.com/evhbejpj 11:22:10 PM July 17, 2010 from TweetDeck
- Ik denk niet dat de ontvangst hier beter van wordt RT @patricksteenks: The Iphone 4 has arrived at #tamtam http://yfrog.com/mv89yj 01:35:17 PM July 15, 2010 from TweetDeck
- Ik voorspel een verlenging..... Zet jouw eigen voorspelling op http://TwitPool.nl/suqg en win een Sharp 46"LCD #wk2010 #oranje #ned 09:26:28 AM June 28, 2010 from Twitpool.nl Oranje WK2010 Pool
- Als v Persie 2 min. later had gescoord, en Kuijt niet voor die kameroenees geel was 't kat in 't bakkie geweest voor #twitpool, nu afwachten 09:38:59 PM June 24, 2010 from TweetDeck
- IE9 preview 3 ondersteunt Canvas met hardware acceleratie. Het wordt misschien ooit nog wat met die browser #tamtam 05:47:20 AM June 24, 2010 from TweetDeck
DateTimeField vs. FieldValue in a publishing page
In one of our projects we needed to show the Modified date and time value in publishing page.
Not a big deal you would think. The only issue we had when using a FieldValue control is that the time that would be displayed was 1 or 2 hours later than the actual value.
After I changed this to a DateTimeField the difference was gone.
The only thing you need to add is a ControlMode=”Display” attribute to prevent editors from setting their own value in edit mode.
The difference is in the way the value is rendered. The FieldValue control does a ToString() and HtmlEncode on the value. The DateTimeField actually converts the value to local time by using the TimeZone class.
It’s all in the details!
No related posts.