Bug 15907 - DateTimeOffset.AddDays ArgumentException
Summary: DateTimeOffset.AddDays ArgumentException
Alias: None
Product: Class Libraries
Classification: Mono
Component: mscorlib ()
Version: 2.8.x
Hardware: PC Windows
: --- normal
Target Milestone: Untriaged
Assignee: Marek Safar
Depends on:
Reported: 2013-11-04 13:14 UTC by Bill Mauer
Modified: 2013-11-12 03:52 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Bill Mauer 2013-11-04 13:14:57 UTC
The following line, when called with Daylight Savings between Now and the resultant DateTimeOffset will produce the exception given:

System.DateTimeOffset threshold = System.DateTimeOffset.Now.AddDays(-7);

Exception: ArgumentException: dateTime.Kind equals Local and offset does not equal the offset of the system's local time zone.
Call stack:
System.DateTimeOffset..ctor (DateTime dateTime, TimeSpan offset)
System.DateTimeOffset.AddDays (Double days)

To be more clear, if Daylight Savings were on November 3rd, then running this code with a current date of November 4th-9th (and some of the 10th) would result in this exception.
Comment 1 Marek Safar 2013-11-12 03:52:44 UTC
This seems to be fixed in mono 3.2