C#

static System.Windows.Forms.Timer tmr = new System.Windows.Forms.Timer(); // Your timer

int iCurrentSeconds = 0;

private void NotificationConfig_Load(object sender, EventArgs e)
{
   tmr.Tick += new EventHandler(TimerEventProcessor); // Timer event handler
   tmr.Interval = 1000; // 1 second       
   tmr.Start(); // Start the timer
}

private void TimerEventProcessor(object obj, EventArgs e)
{
   iCurrentSeconds++; // Adds one second to the second counter for every interval
   Console.Writeline("Timer has been running for {0} seconds!", iCurrentSeconds); // writes how many seconds the timer has ran to console
}

Pete O`Hanlon wrote:

Why do you actually need to do this? It seems a lot more complicated than getting the difference between two datetime objects. It's certainly a lot more code - which while not always a bad thing, certainly doesn't adhere to the KISS principal.

Justin Perez wrote:

I assumed that he was wanting to preform an operation multiple times within the timer, until a certain condition had been met. The most simple way to do that to me seemed to be a timer preforming the operations, and when the condition was met, do a timer.Stop().

Justin Perez wrote:

Maybe I am missing something though, is it as efficent to do the above with a TimeSpan object?

Pete O`Hanlon wrote:

There's a bit of a gotcha with a TimeSpan in that you can't go over a day. Now I know it's unlikely, but it is vaguely possible that he started the process off and then left to go on holiday for a couple of weeks. When he gets back, if he's using the DateTime it will work - a TimeSpan and it'll crash.

Pete O`Hanlon wrote:

OK - slap me round the head with a wet kipper. I'm just plain wrong here. I've just had a quick look and the TimeSpan class does indeed allow you to use a greater range. So - saying this, I'd go with the TimeSpan object.

Thanks for making me go and have a look again. Worth a 5 for making me look an idiot.

Justin Perez wrote:

That's why I love codeproject.