You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by "Dominik Psenner (JIRA)" <ji...@apache.org> on 2015/04/01 08:28:53 UTC

[jira] [Comment Edited] (LOG4NET-412) Millisecond always return 0 in wince

    [ https://issues.apache.org/jira/browse/LOG4NET-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390067#comment-14390067 ] 

Dominik Psenner edited comment on LOG4NET-412 at 4/1/15 6:28 AM:
-----------------------------------------------------------------

I almost am convinced that if the operating system / framework / whoever does not report milliseconds, log4net shouldn't try to do fancy things that might make the situation even worse. After all we will never be able to calculate a "good" value if the hardware lacks the capabilities.


was (Author: nachbarslumpi):
I almost am convinced that if the operating system / framework / whoever does not report milliseconds, log4net shouldn't try to do fancy things that might make the situation even worse.

> Millisecond always return 0 in wince 
> -------------------------------------
>
>                 Key: LOG4NET-412
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-412
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 1.3.0
>         Environment: NETCF
>            Reporter: Son Tran
>            Priority: Trivial
>              Labels: DateTime,
>
> As I check the DateTime.Ticks is used in function AbsoluteTimeDateFormatter.FormatDate always return 0
> work around by using Enviroment.TichCount.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)