Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved DateTime parameter issue with DotNetAssembly

  1. Issue
0
Votes
Undo
  1. Jeff Martin
    Jeff Martin
  2. PowerBuilder
  3. Wednesday, 9 March 2022 15:12 PM UTC

I have a C# class with a method that takes a DateTime parameter. When called from PB using the DotNetAssembly + DotNetObject objects introduced in PB2019 R2, the variable when recieved in the .NET side does not have the milliseconds that were passed in. Is this a known issue?

PBAutoBuild Crashes Depending on the Length of a L...
PowerClient - Desktop LNK/Shortcut Text Value?
Responses (2)
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Thursday, 10 March 2022 15:17 PM UTC
  2. PowerBuilder
  3. # 1

A side note:

The .Net version 6 which recently came out introduced DateOnly and TimeOnly data types which would match with PowerBuilder Date and Time data types.

I would hope that these are supported as well.

Comment
Mark Lee @Appeon
  1. Mark Lee @Appeon
  2. Friday, 11 March 2022 02:38 AM UTC
Hi Roland,



Thanks for your feedback.

I will also transfer it to our development team to consideration.
  1. Helpful
There are no comments made yet.
Mark Lee @Appeon
Mark Lee @Appeon Accepted Answer Pending Moderation
  1. Thursday, 10 March 2022 05:39 AM UTC
  2. PowerBuilder
  3. # 2

Hi Jeff,

 

Thanks for reporting this problem.

Yes, currently, it doesn't support this usage. 

I suggest that you use a string type to replace the datetime type as the parameter to work around this issue.

In the meantime, I will submit this issue to the development to consider adding the support of milliseconds in a future release.  

 

Regards,

 

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.