[jira] [Commented] (LOG4NET-412) Millisecond always return 0 in wince
[ https://issues.apache.org/jira/browse/LOG4NET-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392367#comment-14392367 ] Son Tran commented on LOG4NET-412: -- many CF in medical devices (Radiography, Fluoroscopy, Ultrasound control panel). it regualarly restart per day:D 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)
[jira] [Commented] (LOG4NET-412) Millisecond always return 0 in wince
[ https://issues.apache.org/jira/browse/LOG4NET-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14390067#comment-14390067 ] Dominik Psenner commented on LOG4NET-412: - 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)
[jira] [Commented] (LOG4NET-412) Millisecond always return 0 in wince
[ https://issues.apache.org/jira/browse/LOG4NET-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14390567#comment-14390567 ] Stefan Bodewig commented on LOG4NET-412: I tend to agree. 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)
[jira] [Commented] (LOG4NET-412) Millisecond always return 0 in wince
[ https://issues.apache.org/jira/browse/LOG4NET-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14390566#comment-14390566 ] Stefan Bodewig commented on LOG4NET-412: Hmm, after about 25 days Environment.Ticks starts to wrap around and returns negative values. I'm not sure where you find CF nowadays, but I wouldn't rely on those systems restarting regularly :-) 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)
[jira] [Commented] (LOG4NET-412) Millisecond always return 0 in wince
[
https://issues.apache.org/jira/browse/LOG4NET-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14390021#comment-14390021
]
Son Tran commented on LOG4NET-412:
--
Above code hang when run out of battery.
so I use simple wrap of Environment.TickCount like this
public static DateTimeCF
{
private static DateTime m_start = DateTime.Now;
private static m_startTickCount = Environment.TickCount;
public static DateTime Now
{
return m_start.AddMilliseconds(Environment.TickCount - m_startTickCount);
}
}
and I change in LoggingEvent to
#if !NETCF
m_data.TimeStamp = DateTime.Now;
#else
m_data.TimeStamp = DateTimeCF.Now;
#endif
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)
[jira] [Commented] (LOG4NET-412) Millisecond always return 0 in wince
[ https://issues.apache.org/jira/browse/LOG4NET-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386439#comment-14386439 ] Stefan Bodewig commented on LOG4NET-412: I've found the code you use in http://blog.opennetcf.com/ctacke/archives/ms-Resolution%20DateTime.pdf - unfortunately the license of that code is totally unclear to me. 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)
