NASTY Bug in handling of DateTime.MaxValue and DateTime.MinValue

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Here's a good one (we scratched our heads for an hour before a LAN trace pointed us in the right direction)

1) Create a web service with a parameter of type DateTime
2) Call it with a parameter value of DateTime.MaxValue, from another machine whose timezone is west of you
*or
2) Call it with a parameter value of DateTime.MinValue, from another machine whose timezone is east of you

Enjoy

-Bil
 
Hi, Bill,

Could you please include the resulting and expected behavior, so we can
route the issue in the right direction?

Thanks,
Katy King
CLR BCL Test

--------------------
From: "=?Utf-8?B?YmlsbF83Nw==?=" <[email protected]>
| Here's a good one (we scratched our heads for an hour before a LAN trace
pointed us in the right direction):
|
|1) Create a web service with a parameter of type DateTime.
|2) Call it with a parameter value of DateTime.MaxValue, from another
machine whose timezone is west of you.
|*or*
|2) Call it with a parameter value of DateTime.MinValue, from another
machine whose timezone is east of you.
|
|Enjoy.
|
|-Bill
|
|
 
I think he expects the DateTime structure to handle times that are either
before MinValue or after MaxValue. He doesn't seem to understand what those
properties mean.

Jerry
 
Back
Top