.NET 2.0's Stopwatch Class, and the End of the Moving Story

Doing a lot of writing over the past ten years, but to be honest, this is the piece I'm happiest with so far. The technology discussed is awfully simply (the System.Diagnostics.Stopwatch class in .NET 2.0), but the final leg of the moving story came out as well as anything I'm going to write. Drop by Code Magazine's site for the finale of the three-part cross-country move story. While you're there, why not peruse some of the other articles? Even better, subscribe to the printed magazine! (Yes, it's a plug. But I can try, can't I?)

For those that are coming in late, here are the links to the entire series of three whine-fest/articles dealing with the big move. Really, there are some coding issues buried in there:

Are We There Yet? (Part 3) (May/Jun 2005)

Stay Put. Understand Your Space (Part 2) (Mar/Apr 2005)

Elegant Isn't Always Best (Part 1) (Jan/Feb 2005)

 

Published Friday, April 22, 2005 5:19 AM by KenG

Comments

Sunday, April 24, 2005 5:06 AM by Daniel Moth

# re: .NET 2.0's Stopwatch Class, and the End of the Moving Story

Quote from article:
“and automatically uses a less accurate timer if it must (on mobile devices, for example)”

Two points:
1. Stopwatch is not supported by CF 2.0 so the “mobile devices” comment doesn’t apply.
2. The higperformancecounter is supported by some CE devices (e.g. ours). In fact I have written a Stopwatch class for .NET 1.1 and NETCF 1.0/2.0
http://www.danielmoth.com/Blog/2004/12/stopwatch.html
Sunday, April 24, 2005 6:06 AM by KenG

# re: .NET 2.0's Stopwatch Class, and the End of the Moving Story

Daniel:

Cool. Thanks. I haven't spent any time with CF 2.0, and so was going by what I inferred from the help topics. Glad to get the correct information. -- Ken