Is it possible there is a bug with the System.TimeSpan object in .NET?
I am using it to track times and am seeing an unusual situation.
From what I understand, there are 1000 milliseconds in a second. I
have a test I ran using the TimeSpan object which when I use
TimeSpan.Milliseconds I got 658 but if I use TimeSpan.Seconds I get 5.
If it took 658 milliseconds that should be less than 1 second right?
658 milliseconds should not convert to 5 seconds should it?