home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
Electronic Program Guide
WebEPG
WebEpg development
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="doskabouter" data-source="post: 1074710" data-attributes="member: 98267"><p>Well, I've seem to start quite a discussion. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p> </p><p>To react to Tony's quite thoroughly explanation:</p><p>I think I didn't make myself 100% clear.</p><p>Of course I'll use DateTimeOffset instead of DateTime if that's better, but my main question was about what to parse and validate.</p><p>Do I stick to UTC only for parsing, or anything that .NET will validate?</p><p> </p><p><span style="font-size: 9px">And for the record, one of the things I learned in my 20+ years of software development is knowing when to be cautious!</span></p><p> </p><p>As for the contents of databases (in fact any persistant storage): +1 for UTC</p></blockquote><p></p>
[QUOTE="doskabouter, post: 1074710, member: 98267"] Well, I've seem to start quite a discussion. :) To react to Tony's quite thoroughly explanation: I think I didn't make myself 100% clear. Of course I'll use DateTimeOffset instead of DateTime if that's better, but my main question was about what to parse and validate. Do I stick to UTC only for parsing, or anything that .NET will validate? [SIZE=1]And for the record, one of the things I learned in my 20+ years of software development is knowing when to be cautious![/SIZE] As for the contents of databases (in fact any persistant storage): +1 for UTC [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Electronic Program Guide
WebEPG
WebEpg development
Contact us
RSS
Top
Bottom
