Timer vs. Timer [Resolved]

What is the pros and cons of using the Timer ocx
vs using a Timer class?

Thanks.

Nothing. They're both of type System.Windows.Forms.Timer

Ok, I just asked because in VB6 the ocx was unreliable and using
the APIs were more accurate.

Also, I seen that in some of the 101 demos they dont use the ocx
Timer.

Thanks.

I don't know if you know this, but a little different in this case...

Look at it this way: You can instantiate a Label object, and then place it on your form using code. OR, you can drag it onto your form at design time and the code is in that hidden Code Region. Either way, the same code is used. No APIs involved here, just the same class being instantiated, property values added, and voila!


I'd suppose its a matter of preference. A better example is that some people like to create their dataadapters and datasets by dragging it off the server tab. Most of us here on the forums like to do it through code. We're accomplishing the same thing, only difference being one is visual, the other is not.

Yes, its all starting to come together now. I've seen the code in
the "Windows Form Designer generated code" and now I get it.

And again, Thanks.