Comments for Olivier's Blog http://odalet.wordpress.com Dieu a inventé le chat pour que l’homme puisse caresser le tigre Fri, 23 Oct 2009 07:06:32 +0000 http://wordpress.com/ hourly 1 Comment on Saving the state of a Graphics object by Bob52 http://odalet.wordpress.com/2006/08/23/saving-the-state-of-a-graphics-object/#comment-11746 Bob52 Fri, 23 Oct 2009 07:06:32 +0000 https://odalet.wordpress.com/2006/08/23/saving-the-state-of-a-graphics-object/#comment-11746 I actually opted for two answers depending on whether the averaging is done on distance or time. , I actually opted for two answers depending on whether the averaging is done on distance or time. ,

]]> Comment on Saving the state of a Graphics object by Coder16 http://odalet.wordpress.com/2006/08/23/saving-the-state-of-a-graphics-object/#comment-11745 Coder16 Thu, 22 Oct 2009 07:28:13 +0000 https://odalet.wordpress.com/2006/08/23/saving-the-state-of-a-graphics-object/#comment-11745 Avoid those miserable colds. , Avoid those miserable colds. ,

]]> Comment on Log4Net: IP parsing bug when used with framework .NET 2.0 by The devva.net blog | log4net UdpAppender on IPv6 (Windows 2008, Vista or 7) http://odalet.wordpress.com/2007/01/13/log4net-ip-parsing-bug-when-used-with-framework-net-20/#comment-11741 The devva.net blog | log4net UdpAppender on IPv6 (Windows 2008, Vista or 7) Tue, 06 Oct 2009 20:07:01 +0000 http://odalet.wordpress.com/2007/01/13/log4net-ip-parsing-bug-when-used-with-framework-net-20/#comment-11741 [...] at least) and that is something that didn't make it into the log4net 1.2.10 release. There are some fixes to log4net, but the 1.2.10 version is compiled into loads of other framworks that I'm using and compiling an [...] [...] at least) and that is something that didn't make it into the log4net 1.2.10 release. There are some fixes to log4net, but the 1.2.10 version is compiled into loads of other framworks that I'm using and compiling an [...]

]]> Comment on Log4Net: IP parsing bug when used with framework .NET 2.0 by Using LogView4Net with EPiServer | Fredrik Haglund's blog http://odalet.wordpress.com/2007/01/13/log4net-ip-parsing-bug-when-used-with-framework-net-20/#comment-11701 Using LogView4Net with EPiServer | Fredrik Haglund's blog Tue, 02 Sep 2008 11:14:24 +0000 http://odalet.wordpress.com/2007/01/13/log4net-ip-parsing-bug-when-used-with-framework-net-20/#comment-11701 [...] appears that there is are issues in net 2.0 with IPv6 interfering with the parsing of the remoteAddress but the bug fix appear not to [...] [...] appears that there is are issues in net 2.0 with IPv6 interfering with the parsing of the remoteAddress but the bug fix appear not to [...]

]]> Comment on Log4Net: IP parsing bug when used with framework .NET 2.0 by Olivier http://odalet.wordpress.com/2007/01/13/log4net-ip-parsing-bug-when-used-with-framework-net-20/#comment-11595 Olivier Thu, 21 Aug 2008 14:07:33 +0000 http://odalet.wordpress.com/2007/01/13/log4net-ip-parsing-bug-when-used-with-framework-net-20/#comment-11595 Thank you SergeS! Just after having read your comment I checked the log4net repository and jira (https://issues.apache.org/jira/browse/LOG4NET-112). And the source code has been modified in the same way that your proposition. Thank you SergeS!

Just after having read your comment I checked the log4net repository and jira (https://issues.apache.org/jira/browse/LOG4NET-112). And the source code has been modified in the same way that your proposition.

]]> Comment on Log4Net: IP parsing bug when used with framework .NET 2.0 by SergeS http://odalet.wordpress.com/2007/01/13/log4net-ip-parsing-bug-when-used-with-framework-net-20/#comment-11588 SergeS Thu, 21 Aug 2008 00:45:57 +0000 http://odalet.wordpress.com/2007/01/13/log4net-ip-parsing-bug-when-used-with-framework-net-20/#comment-11588 Problem is not with IPAddressConverter. All you need is fix two lines in 'UdpAppender::InitializeClientConnection()', so that both 'new UdpClient()' calls use 'RemoteEndPoint.AddressFamily' parameter as well. With this fix both IP4 and IP6 working OK. Problem is not with IPAddressConverter.

All you need is fix two lines in ‘UdpAppender::InitializeClientConnection()’, so that both ‘new UdpClient()’ calls use ‘RemoteEndPoint.AddressFamily’ parameter as well.

With this fix both IP4 and IP6 working OK.

]]> Comment on Pattern singleton thread safe en C# : c’est facile by Olivier http://odalet.wordpress.com/2006/06/20/pattern-singleton-thread-safe-en-c-cest-facile/#comment-11395 Olivier Thu, 31 Jul 2008 20:41:20 +0000 https://odalet.wordpress.com/2006/06/20/pattern-singleton-thread-safe-en-c-cest-facile/#comment-11395 Eh Antoine, n'en fais pas trop quand même ! Eh Antoine, n’en fais pas trop quand même !

]]> Comment on Pattern singleton thread safe en C# : c’est facile by Ant http://odalet.wordpress.com/2006/06/20/pattern-singleton-thread-safe-en-c-cest-facile/#comment-11394 Ant Thu, 31 Jul 2008 13:57:00 +0000 https://odalet.wordpress.com/2006/06/20/pattern-singleton-thread-safe-en-c-cest-facile/#comment-11394 Merci ça m'a trop aidé dans un développement dans un contexte multithreadé, préemptif avec intropsection multiprotocole. Par contre il faut lire la ligne : public static Instance { get { return instance; } } commme : public static MySingleton Instance { get { return instance; } } Merci ça m’a trop aidé dans un développement dans un contexte multithreadé, préemptif avec intropsection multiprotocole.

Par contre il faut lire la ligne :
public static Instance { get { return instance; } }

commme :

public static MySingleton
Instance { get { return instance; } }

]]> Comment on The "using" pattern by TibO http://odalet.wordpress.com/2007/03/12/the-using-pattern/#comment-11389 TibO Mon, 07 Jul 2008 12:28:10 +0000 http://odalet.wordpress.com/2007/03/12/the-using-pattern/#comment-11389 Oo lol, jte kif tro mdr ^^ Oo lol, jte kif tro mdr ^^

]]> Comment on The "using" pattern by JF Totain http://odalet.wordpress.com/2007/03/12/the-using-pattern/#comment-11388 JF Totain Mon, 07 Jul 2008 12:24:20 +0000 http://odalet.wordpress.com/2007/03/12/the-using-pattern/#comment-11388 LoL laché vo kom ! LoL laché vo kom !

]]>