DateTime FAQ Entries

BCL Team Blog DateTime FAQ Entries | home lighting

BCL Team Blog DateTime FAQ Entries | home lighting — Sun, 14 Jun 2009 04:54:18 GMT

PingBack from http://homelightingconcept.info/story.php?id=154

BCL Team Blog DateTime FAQ Entries | Cellulite Creams

BCL Team Blog DateTime FAQ Entries | Cellulite Creams — Tue, 09 Jun 2009 05:47:34 GMT

PingBack from http://cellulitecreamsite.info/story.php?id=11613

BCL Team Blog DateTime FAQ Entries | Best Eye Cream

BCL Team Blog DateTime FAQ Entries | Best Eye Cream — Mon, 08 Jun 2009 05:43:59 GMT

PingBack from http://besteyecreamsite.info/story.php?id=2872

BCL Team Blog DateTime FAQ Entries | Paid Surveys

BCL Team Blog DateTime FAQ Entries | Paid Surveys — Fri, 29 May 2009 20:18:02 GMT

PingBack from http://paidsurveyshub.info/story.php?title=bcl-team-blog-datetime-faq-entries

Ciaran’s Random Writings » Blog Archive » The Rise and Fall of Microsoft Development Tools, Part 1

Fri, 24 Aug 2007 18:38:55 GMT

PingBack from http://blog.ciarang.com/index.php/archives/19

More DateTime related discussions during pre-Whidbey release

Kathy Kam — Fri, 28 Jul 2006 00:24:42 GMT

While doing my System.DateTime and System.TimeZone investigation, I come across some old discussions...

Date

Hackward and Foreword — Sun, 31 Oct 2004 22:28:00 GMT

re: DateTime FAQ Entries

Shital Shah — Wed, 28 Jul 2004 19:46:00 GMT

There is one serious problem in your recommandation to store date time format as "yyyy-MM-ddTHH:mm:ss.fffffff". This format is not acceptable by lots of COM code written in VB6, VBScript and VBA function (you always find these things in enterprise environment in obscure places like VBA functions in Access queries). The reason these functions fails is because,

1. They don't like fractional seconds part.
2. The "T" as seperator between date and time is not acceptable in some non-English local like Dutch. For example DateValue() call in VBA/VB6/VBScript getting executed in Netherlands will fail if you feed data generated by .Net program in above format.

The format that you should use if you want your data to be readable in all worlds is this:

"yyyy-MM-dd HH:mm:ss"

Yes, you loose fractions of seconds but in a realistic world, this is the only format I've found that works in all different locals with .Net and with VB6 COM and VBScript and VBA.

It would be really good to add a shortcut for this format in Whidbey because most people aren't aware of this. Its too late when you get a call from Japan that your new data generated from glorious .Net app doesn't go hand in hand with their queries fired on linked tables in Access :).

Regards,
Shital.
http://www.ShitalShah.com

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Whenever people say "we mustn't be sentimental", you can take it they are about to do something cruel. And if they add, "we must be realistic", they mean they are going to make money out of it.

-Brigid Brophy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

re: DateTime FAQ Entries

dianying xia zai — Mon, 26 Jul 2004 10:12:00 GMT

dianying xia zai:http://www.kamun.com/
movie down:http://movie.kamun.com/
mp3 xia zai:http://music.kamun.com/
engage:http://club.kamun.com/

re: DateTime FAQ Entries

Kit George [MSFT] — Tue, 13 Jul 2004 21:52:00 GMT

This code should do you the trick James:

using System;
using System.Threading;
using System.Globalization;

public class Temp {
public static void Main() {
DateTime dt = DateTime.Now;
Console.WriteLine(Thread.CurrentThread.CurrentCulture.

DateTimeFormat.MonthNames[dt.Month - 1]);

}
}