You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
.NET Command Line Tools (1.0.0-preview2-003131)
Product Information:
Version: 1.0.0-preview2-003131
Commit SHA-1 hash: 635cf40e58
Runtime Environment:
OS Name: Mac OS X
OS Version: 10.12
OS Platform: Darwin
RID: osx.10.12-x64
.NET Command Line Tools (1.0.0-preview2-003131)
Product Information:
Version: 1.0.0-preview2-003131
Commit SHA-1 hash: 635cf40e58
Runtime Environment:
OS Name: Windows
OS Version: 10.0.14393
OS Platform: Windows
RID: win10-x64
using System;publicclassSubItem{publicstringStringValue{get;set;}publicint?IntegerValue{get;set;}publicDateTime?DateValue{get;set;}publicbool?BooleanValue{get;set;}}publicclassProgram{publicstaticvoidMain(){varsubItem=new SubItem();
subItem.DateValue = DateTime.Now;
Console.WriteLine(subItem.DateValue);}}
Could you share a complete program that demonstrates the issue? How exactly are you viewing the value? Are you using some debugger or IDE? Are you sure your machine has the correct time set?
@tongqijie commented on Fri Mar 03 2017
i have a class contains a property whose type is DateTime?
i set value to property 'DateValue' like this:
the problem is that subItem.DateValue is always {01/01/0001 00:07:28}. why?
please help me...
@tongqijie commented on Fri Mar 03 2017
here is my dotnet --info:
@tongqijie commented on Fri Mar 03 2017
it works fine on windows.
@svick commented on Sat Mar 04 2017
The following code works fine for me on Linux:
Could you share a complete program that demonstrates the issue? How exactly are you viewing the value? Are you using some debugger or IDE? Are you sure your machine has the correct time set?
@tongqijie commented on Sat Mar 04 2017
today, i found it worked fines, but it was weird to watch variable's value when debugging.
@svick commented on Sat Mar 04 2017
I can see the same behavior in VS Code on Linux.
I believe this is dotnet/vscode-csharp#753, which is in turn caused by https://github.com/dotnet/coreclr/issues/7115, which should be fixed in the next version of .Net Core. But it is only a debugging bug, so it shouldn't affect how your application actually executes.
The text was updated successfully, but these errors were encountered: