ApplicationData.Current.LocalSettings and DateTimeOffset.MinValue

Hong 1,046

  ApplicationDataContainer localSettings = ApplicationData.Current?.LocalSettings;
  localSettings.Values["foo"] = DateTimeOffset.MinValue;
  DateTimeOffset dto = (DateTimeOffset)localSettings.Values["foo"];

The last line of the above code throws the following exception

"Specified argument was out of the range of valid values."

   at System.DateTime.ToLocalTime(Boolean throwOnOverflow)
   at System.DateTimeOffset.ToLocalTime(Boolean throwOnOverflow)
   at System.StubHelpers.DateTimeOffsetMarshaler.ConvertToManaged(DateTimeOffset& managedLocalDTO, DateTimeNative& nativeTicks)
   at System.Runtime.InteropServices.WindowsRuntime.IReference`1.get_Value()
   at System.Runtime.InteropServices.WindowsRuntime.CLRIReferenceImpl`1.UnboxHelper(Object wrapper)
   at System.StubHelpers.InterfaceMarshaler.ConvertToManaged(IntPtr pUnk, IntPtr itfMT, IntPtr classMT, Int32 flags)
   at System.Runtime.InteropServices.WindowsRuntime.IMap`2.Lookup(K key)
   at System.Runtime.InteropServices.WindowsRuntime.MapToDictionaryAdapter.Lookup[K,V](IMap`2 _this, K key)

What is the range of valid values?

Fay Wang - MSFT 5,196 Reputation points

2019-12-23T02:35:45.807+00:00

When I tested the above code, it worked well. What's the value of your DateTimeOffset.MinValue? If you create a blank project to use the three lines of code, will the same issue occur? And what is the version number of your system and visual studio?
Hong 1,046 Reputation points

2019-12-23T15:24:52.74+00:00

Thank you for looking into this.
DateTimeOffset.MinValue = {0001-01-01 12:00:00 AM +00:00}

From a blank project:

Microsoft Visual Studio Enterprise 2019
Version 16.4.1
VisualStudio.16.Release/16.4.1+29609.76
Microsoft .NET Framework
Version 4.8.03752

Installed Version: Enterprise

Architecture Diagrams and Analysis Tools 00433-90000-00004-AA783
Microsoft Architecture Diagrams and Analysis Tools
Fay Wang - MSFT 5,196 Reputation points

2019-12-24T09:00:29.523+00:00

When I used the same version to create a blank app and tested the three lines of code, it worked well. So can you provide a simple sample that can be reproduced for us to test? And can you show the detailed repro steps?
Fay Wang - MSFT 5,196 Reputation points

2019-12-27T08:40:55.227+00:00

Hi, is there any update? Do you solve issue? If not, can you provide a simple sample?
Hong 1,046 Reputation points

2019-12-27T14:55:05.443+00:00

Here is the barebone app that I used to reproduce this problem.
Fay Wang - MSFT 5,196 Reputation points

2019-12-30T09:36:16.48+00:00

When I tested it, I still can't reproduce this issue, it worked well. If you test it in aother machine, will the same issue occur?
Hong 1,046 Reputation points

2019-12-31T06:18:23.517+00:00

Thanks a lot for testing it. This is really weird.
Fay Wang - MSFT 5,196 Reputation points

2020-01-02T07:29:50.12+00:00
I noticed your operating system is windows 10 pro, if you test the code in windows 10 Enterprise machine, will the same issue occur? In addition, you can use the following code snippet to replace your code. Directly pass the DateTimeOffset.MinValue to dto to achieve assignment. Actually, the value of DateTimeOffset.MinValue is fixed, can be assigned directly to dto, why do you want to save it in localsetting and then assign?

ApplicationDataContainer localSettings = ApplicationData.Current?.LocalSettings; localSettings.Values["foo"] = DateTimeOffset.MinValue; DateTimeOffset dto = DateTimeOffset.MinValue;