hamang.net » Tools http://hamang.net - the everyday life Wed, 10 Feb 2010 09:52:49 +0000 http://wordpress.org/?v=2.9.1 en hourly 1 Resharper Team Blog http://hamang.net/2006/06/16/resharper-team-blog/ http://hamang.net/2006/06/16/resharper-team-blog/#comments Fri, 16 Jun 2006 11:07:03 +0000 Knut Hamang Can't live without it. Developing without resharper is like drinking a beer with a straw. It's possible, but slow. And to be honest refactoring in Visual Studio 2005 sucks. It's a lightweight implementation of refactoring, and it's slow. Compare "Find usages" in VS 2005 with resharper and I think you get the point.

Ok, resharper has a lot of bugs, but it will become more stable in the near future. Anyway, check out the new Team Blog for resharper.

]]> http://hamang.net/2006/06/16/resharper-team-blog/feed/ 0 Wrong timestamp in the Enterprise Application Logging block http://hamang.net/2006/06/15/wrong-timestamp-in-the-enterprise-application-logging-block/ http://hamang.net/2006/06/15/wrong-timestamp-in-the-enterprise-application-logging-block/#comments Thu, 15 Jun 2006 14:19:25 +0000 Knut Hamang If you have tried the standard implementation of the SimpleFormatter in Enterprise Library Logging block, you will notice that timestamps are not what they should have been (depending on where you live in the world, of course;) ) . In Norway, for instance, the timestamp is 2 hours wrong. This is actually by design, since logging should be time independent and use UTC time. Anyway, in my opinion this should be configurable by default, but it seems the only way around is to write your own, or extend the SimpleFormatter.

Tom Hollander writes about the solution in his blog.

BTW, make sure you use the rolling file trace listener by Erwyn van der Meer. It's excellent for not having one HUGE log file.

]]> http://hamang.net/2006/06/15/wrong-timestamp-in-the-enterprise-application-logging-block/feed/ 0 Strongly naming the Microsoft Enterprise Library http://hamang.net/2006/03/03/strongly-naming-the-microsoft-enterprise-library/ http://hamang.net/2006/03/03/strongly-naming-the-microsoft-enterprise-library/#comments Fri, 03 Mar 2006 13:38:14 +0000 Knut Hamang I suppose you have tried the Enterprise Library from Microsoft. You probably also used it in a project that should be strongly named. Seems like the compiled DLL's in Eneterprise Library are not Strongly named! Well, the intention is that, as long as the source code is shipped with Enterprise Library, the DLL's are not Strongly named. You have to do it yourself. Fair enough, and the solution is described in Tom Hollander's blog:

http://blogs.msdn.com/tomholl/archive/2005/04/05/405764.aspx

If you still can't figure it out, here are the gory details:

http://blogs.msdn.com/tomholl/archive/2005/12/02/499529.aspx#502110

]]> http://hamang.net/2006/03/03/strongly-naming-the-microsoft-enterprise-library/feed/ 0