Why throw; is not allways the best way to rethrow exceptions
posted by malovicn(1590) 4 years, 5 months ago 0
Senfo, in case you would like to log exception (e.g. create event log with Log4Net , Ent Lib block) you would catch - publish - rethrow to preserve information about it. You can do that offcourse on one centralized place, but still you need to try catch publish :D Even in case you don't want to wrap the exception to some custom type, I would still use inner exception because if you don't you loose a piece of stack related to defect. That's the whole point of the blog post - loosing of stack information
Reply
Performance comparison between Linq, NHibernate and Stored Procs
posted by malovicn(1590) 4 years, 4 months ago 0
Rico Mariani performance super guru blogged about same subject in 5 part posts Here's linq to Post No 4 http://blogs.msdn.com/ricom/archive/2007/07/05/dlinq-linq-to-sql-performance-part-4.aspx
Disable .pdb file generation in Release Mode
posted by malovicn(1590) 4 years, 3 months ago 0
I would think twice before doing this, because doing that would leave you out of sustaining data and you won't get any performance gains (build is already optimized) More details about release build pdb : http://blog.vuscode.com/malovicn/archive/2007/08/05/releasing-the-build.aspx
Dependency Injection is Dead!
posted by malovicn(1590) 3 years, 10 months ago 0
PostSharp rocks!