LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LV8.6.1 - Error in specifying System.DateTime constructor MSCORLIB(2.0.0.0)

I have run into an issue when trying to select the System.DateTime(Int32 year, Int32 month, Int32 day, Int32 hour, Int32 minute, Int32 second, Int32 millisecond) .NET constructor in MSCORLIB(2.0.0.0).  All input parameters for this contructor show correctly except the last one.  It shows "kind" instead of "millisecond".  Moreover, two contructors are checked in the selection list when picking either one of the contructors shown in the picture.  All the other selections appear to work correctly.  I tried using the millisecond input assuming it might work anyway.  It does not and the contructor errors out.

 

DateTime Contructor Error

 

 

Is there a fix to this?

 

Thank you.

0 Kudos
Message 1 of 7
(3,673 Views)

The documentation for that DateTime is at http://msdn.microsoft.com/en-us/library/system.datetime.aspx#Y0

 

DateTimeKind is an enumeration.

 

 

0 Kudos
Message 2 of 7
(3,660 Views)

Thank you for the reply.

 

I have read that MSDN already.

 

However, I am trying to use the contructor with milliseconds not the one with DateKind.  When I try to select the contructor with milliseconds it automatically selects both constructors and displays only the one with "kind" on the block diagram.

 

Thank you,

0 Kudos
Message 3 of 7
(3,657 Views)

Hi rkball74,

 

I was able to reproduce the behavior you are talking about. I'm going to escalate this and possibly file a CAR. There is no fix for this right now, but you may be able to work around the issue by using more inputs (if possible). The millisecond input seems to work if you also add the Calendar Calendar input or the DateTimeKind input listed later in the list. I'll post any new information I can find on this issue, and please let me know if you cannot find a workaround.

Zach P.

Staff Software Engineer | LabVIEW R&D | National Instruments
0 Kudos
Message 4 of 7
(3,648 Views)

Just wanted to let you know I filed a CAR on this today.

 

CAR# 348458

Zach P.

Staff Software Engineer | LabVIEW R&D | National Instruments
0 Kudos
Message 5 of 7
(3,631 Views)

Thank you.

0 Kudos
Message 6 of 7
(3,622 Views)

CAR 348458 discussed in this thread has been fixed in LabVIEW 2013. For a more complete list of bugs fixed in LabVIEW 2013, check the LabVIEW 2013 Bug Fixes. You can download an evaluation copy of LabVIEW 2013 at http://www.ni.com/trylabview/ or if you have an earlier version of LabVIEW installed and an active SSP subscription, you will be able to download the latest version of LabVIEW through NI Update Service.

 

Jeff Peacock

 

Product Support Engineer | LabVIEW R&D | National Instruments

0 Kudos
Message 7 of 7
(3,577 Views)