Unexpected result using DateTime.ParseE xact

[Peter Holschbach]

Hi,

I've the following line of code:

result = DateTime.ParseE xact("1999-12-01T23:59:59Z", "yyyy-MM-ddTHH:mm:ssZ",
CultureInfo.Inv ariantCulture);

where I get in result "result" "02.12.1999 00:59:59" instead of teh
expected "01.12.1999 23:59:59"
Anybody a idea ?

Thanx Peter

[=?ISO-8859-1?Q?Arne_Vajh=F8j?=]

Peter Holschbach wrote:

I've the following line of code:

result = DateTime.ParseE xact("1999-12-01T23:59:59Z",
"yyyy-MM-ddTHH:mm:ssZ",
CultureInfo.Inv ariantCulture);

where I get in result "result" "02.12.1999 00:59:59" instead of teh
expected "01.12.1999 23:59:59"
Anybody a idea ?

result = DateTime.ParseE xact("1999-12-01T23:59:59-5",
"yyyy-MM-ddTHH:mm:ssz", CultureInfo.Inv ariantCulture);

gives the correct result for me (I am in GMT-5).

Arne

[=?windows-1252?Q?Arne_Vajh=F8j?=]

Stephany Young wrote:

You specified 'Z' in the format string ("yyyy-MM-ddTHH:mm:ssZ")
therefore your value string MUST end with a 'Z' otherwise the call to
DateTime.ParseE xact will fail. ParseExact means just that (it must macth
EXACTLY).

The problem is that Z apperently do effect the parsing.

result = DateTime.ParseE xact("1999-12-01T23:59:59",
"yyyy-MM-ddTHH:mm:ss", CultureInfo.Inv ariantCulture);
Console.WriteLi ne(result);
result = DateTime.ParseE xact("1999-12-01T23:59:59Z",
"yyyy-MM-ddTHH:mm:ssZ", CultureInfo.Inv ariantCulture);
Console.WriteLi ne(result);

outputs:

01-12-1999 23:59:59
01-12-1999 18:59:59

Your post indicates that your time zone is 1 hour ahead of UTC which
means tht when it is 11:59:59 PM UTC then it is 12:59:59 AM the next day
in your time zone which is exactly the result you got.

To get the result you want, the format string should, as Arne points
out, be "yyyy-MM-ddTHH:mm:ssz", but your value string should be
"1999-12-01T23:59:59+0".

No.

result = DateTime.ParseE xact("1999-12-01T23:59:59-5",
"yyyy-MM-ddTHH:mm:ssz", CultureInfo.Inv ariantCulture);
Console.WriteLi ne(result);
result = DateTime.ParseE xact("1999-12-01T23:59:59+0",
"yyyy-MM-ddTHH:mm:ssz", CultureInfo.Inv ariantCulture);
Console.WriteLi ne(result);

outputs:

01-12-1999 23:59:59
01-12-1999 18:59:59

Arne

[Stephany Young]

Yes. I seem what you mean.

I wonder if the Z is some sort of indicator included for the military who
use the term Zulu in place of UTC.
"Arne Vajhøj" <ar**@vajhoej.d kwrote in message
news:47******** *************** @news.sunsite.d k...

Stephany Young wrote:

>You specified 'Z' in the format string ("yyyy-MM-ddTHH:mm:ssZ") therefore
your value string MUST end with a 'Z' otherwise the call to
DateTime.Parse Exact will fail. ParseExact means just that (it must macth
EXACTLY).

The problem is that Z apperently do effect the parsing.

result = DateTime.ParseE xact("1999-12-01T23:59:59", "yyyy-MM-ddTHH:mm:ss",
CultureInfo.Inv ariantCulture);
Console.WriteLi ne(result);
result = DateTime.ParseE xact("1999-12-01T23:59:59Z",
"yyyy-MM-ddTHH:mm:ssZ", CultureInfo.Inv ariantCulture);
Console.WriteLi ne(result);

outputs:

01-12-1999 23:59:59
01-12-1999 18:59:59

>Your post indicates that your time zone is 1 hour ahead of UTC which
means tht when it is 11:59:59 PM UTC then it is 12:59:59 AM the next day
in your time zone which is exactly the result you got.

To get the result you want, the format string should, as Arne points out,
be "yyyy-MM-ddTHH:mm:ssz", but your value string should be
"1999-12-01T23:59:59+0".

No.

result = DateTime.ParseE xact("1999-12-01T23:59:59-5",
"yyyy-MM-ddTHH:mm:ssz", CultureInfo.Inv ariantCulture);
Console.WriteLi ne(result);
result = DateTime.ParseE xact("1999-12-01T23:59:59+0",
"yyyy-MM-ddTHH:mm:ssz", CultureInfo.Inv ariantCulture);
Console.WriteLi ne(result);

outputs:

01-12-1999 23:59:59
01-12-1999 18:59:59

Arne

[Cor Ligthert[MVP]]

Stephany,

Zulu comes from Zero. I thought that military was only used in the USA, GMT
is at least in Europe more common for the official UTC. Have I understand it
well that the in my idea very Gemenebest country New Sealand uses as well
"Military"?

I don't by the way understand why Peter wants to get another date then he
has written.

In the very spread area CET it now (Not Summer Time) exactly one our later
then in UTC/GMT/ZULU/Military.

For your information: I wrote "spread area" this is because by instance the
Netherlands should be geographicaly in GMT. However (AFAIK) after the last
war they left it in CET because the whole western part of European continent
is now almost in it.

Cor

[Stephany Young]

No Cor!

Zulu (UTC) comes from the last letter of the NATO phonetic alphabet, (Alpha,
Bravo, Charlie, ..., Xray, Yankee, Zulu).

It is the standard designator for the time base in aviation throughout the
world.

It's got absoulutely nothing to do with CET, the Netherlands, the
Commonwealth or even New Zealand for that matter.
"Cor Ligthert[MVP]" <no************ @planet.nlwrote in message
news:5E******** *************** ***********@mic rosoft.com...

Stephany,

Zulu comes from Zero. I thought that military was only used in the USA,
GMT is at least in Europe more common for the official UTC. Have I
understand it well that the in my idea very Gemenebest country New Sealand
uses as well "Military"?

I don't by the way understand why Peter wants to get another date then he
has written.

In the very spread area CET it now (Not Summer Time) exactly one our later
then in UTC/GMT/ZULU/Military.

For your information: I wrote "spread area" this is because by instance
the Netherlands should be geographicaly in GMT. However (AFAIK) after the
last war they left it in CET because the whole western part of European
continent is now almost in it.

Cor

[Cor Ligthert [MVP]]

Stephany,

GMT/UTC/Militairy is Zero time, as you wrote it has to do with the phonetic
alphabet, however I thought, let I not write that to Stephany, because then
I get a correction.

It is created in Greenwich, there is a nice building that you can see when
you go from London upwards to where Jon Skeet is living at your right side.
That building is at the Zero time of the world.

:-)

Cor

[Cor Ligthert [MVP]]

Doh,

Not to the North, I meant upward sailing on the Thames,

Cor

[Cor Ligthert [MVP]]

Stephany,

And to make even three answers on your message.

The OP is from the CET timezone like me, and therefore his time is 1 hour
later then UTC/CET/Zulu/Zero/Military time.

My later part was as well meant for the OP.

Cor

[Stephany Young]

Again Cor, do the research please!

CET is 1 hour AHEAD of UTC, not BEHIND.
"Cor Ligthert [MVP]" <no************ @planet.nlwrote in message
news:%2******** ********@TK2MSF TNGP05.phx.gbl. ..

Stephany,

And to make even three answers on your message.

The OP is from the CET timezone like me, and therefore his time is 1 hour
later then UTC/CET/Zulu/Zero/Military time.

My later part was as well meant for the OP.

Cor