Thanks Kevin, Erik and Markus. That was quite info...

2009-08-31T00:52:11.008-07:00

Thanks Kevin, Erik and Markus. That was quite informative. The updates have been made to the original post for the benefit of future users and webdevs like me!

First; I totally agree with Kevin that this is a m...

2009-08-30T12:06:43.822-07:00

First; I totally agree with Kevin that this is a messy way of calculating the elapsed time between two DateTimes.

And second. Eric hinted that using DateTime.Now for timing sure is bad. Although the limitation does not lie within the TimeSpan struct, but with the underlying implementation of DateTime.Now. For timing you should use the Stopwatch class in System.Diagnostics. See

The problem with this is that TimeSpan only has a ...

2009-08-29T18:58:50.703-07:00

The problem with this is that TimeSpan only has a resolution of 100ms on an NT4 or better system - which means you can't rely on it being accurate for anything less than that amount, give or take. If you really need accurate timing at those levels, you need the high performance timer APIs or multimedia timer APIs.

The DateTime type implements an operator for subtr...

2009-08-29T10:30:08.093-07:00

The DateTime type implements an operator for subtraction that returns a TimeSpan object. This would be my suggestion:

//-----------
DateTime start = DateTime.Now;
Thread.Sleep(10);
DateTime end = DateTime.Now;
TimeSpan span = end - start;
Console.WriteLine("Ticks: " + span.Ticks);
//-----------

From there, you can access

Comments on DevCurry: Calculate the Seconds, Milliseconds and Microsecon...

Thanks Kevin, Erik and Markus. That was quite info...

First; I totally agree with Kevin that this is a m...

The problem with this is that TimeSpan only has a ...

The DateTime type implements an operator for subtr...