Comments on: Silverlight Stopwatch class in C#

By: Aaron

Aaron — Thu, 29 Apr 2010 20:02:52 +0000

In reply to claudio. @claudio: Whoops! Must have done a search/replace and managed to spell it wrong. Need to spell check my APIs! :) I've fixed the problem. Thanks for the heads-up!

By: claudio

claudio — Sat, 24 Apr 2010 19:19:37 +0000

Hi,
This class will be used in my solution by files shared between Silverlight and .NET 4.0.
So for compatibility issue, you should correct the word Ellapsed with Elapsed. It’s just cosmetic, but it can produce compilation problem in case of shared code.
Anyway Thanx
-Claudio

By: WiredPrairie - Silverlight Stopwatch Class, Part 2

WiredPrairie - Silverlight Stopwatch Class, Part 2 — Fri, 02 Apr 2010 15:35:21 +0000

[…] recently made a fix to a Silverlight stopwatch class I wrote last […]

By: Aaron

Aaron — Fri, 02 Apr 2010 15:24:24 +0000

In reply to Vincent. I've updated the code, and tested it. Thanks all for the suggestions. Not sure why my tests worked when I wrote it.

By: Vincent

Vincent — Fri, 02 Apr 2010 13:46:51 +0000

Fixed functions:

// Timespan expects the value indiciated as 100ns .. thats 1 / 10000 of a ms.
public TimeSpan Ellapsed
{
get { return new TimeSpan( GetCurrentElapsed() * 10000 ); }
}

// GetCurrentElapsed() returns the MS already, no need to adjust that
public long EllapsedMilliseconds
{
get { return GetCurrentElapsed(); }
}

// getting value in milliseconds, gotta recalculate to turn it into ticks
public long EllapsedTicks
{
get { return GetCurrentElapsed() * TimeSpan.TicksPerMillisecond; }
}

By: Vincent

Vincent — Fri, 02 Apr 2010 13:40:17 +0000

There is a mistake. Has been said 3 times by now. this is the 4th. The fact you say the documentation leads you to think its correct, suggest you haven’t tested it nor read the documentation correctly.

http://msdn.microsoft.com/en-us/library/system.environment.tickcount.aspx

Clearly states it returns a value in milliseconds and not ticks.

Other then that, a big thanks for the code :) Works fine after some minor bug fixing

By: Rui Fan

Rui Fan — Wed, 05 Aug 2009 09:15:57 +0000

Pospa and Chad Riddle are saying the samething.
Environment.TickCount is the milliseconds.
From MSDN:
TickCount is different from the Ticks property, which is the number of 100-nanosecond intervals that have elapsed since 1/1/0001, 12:00am.

By: Sree

Sree — Sun, 26 Jul 2009 03:48:43 +0000

Thanks for the code. I could not make it work as is but Chad Riddle’s comments worked for me.

Sree

By: Aaron

Aaron — Wed, 01 Jul 2009 00:39:41 +0000

Popsa — if that’s the case, what would the right answer be? The documentation doesn’t lead me to believe it’s wrong, and that would be an inconsistency in the framework.

By: Pospa

Pospa — Fri, 26 Jun 2009 09:19:58 +0000

There is an error in this implementation. Because TimeSpan.TicksPerMillisecond in mos of cases does not corespondent with ticks/s used for Environment.TickCount computing. You should to review your code.