Browse by Tags

All Tags » Design/Coding Guidance » .NET 2.0 (RSS)
Monday, July 28, 2008 2:00 PM

ITSWITCH #1: Answer

Last post I detailed some code that may or may not have something wrong in it.  If you thought InitializeOne and IntializeTwo are semantically identical (e.g. they differ only by performance), you'd be wrong. If you simply ran the code, you'd...
Posted by PeterRitchie | with no comments
Filed under: , , , , , ,
Friday, July 25, 2008 1:58 PM

ITSWITCH: #1

A short pop quiz on design/coding in C#...
Posted by PeterRitchie | 5 comment(s)
Filed under: , , , , , ,
Wednesday, August 22, 2007 2:13 PM

Thread.Abort is a Sign of a Poorly Designed Program

Continuing the theme of Thead.Sleep is a sign of a poorly designed program , I've been meaning to provide similar detail on Thread.Abort and not just allude to it in other posts like 'System.Threading.Thread.Suspend() is obsolete: 'Thread...
Posted by PeterRitchie | 7 comment(s)
Filed under: , , ,
Thursday, July 12, 2007 9:30 PM

Performance Implications of try/catch/finally, Part Two

In a previous blog entry Performance Implications of try/catch/finally I outlined that the conventional wisdom that there are no performance implications to try blocks unless an exception is thrown is false. I have some clarifications and details to add...
Posted by PeterRitchie | with no comments
Filed under: , , ,
Friday, June 22, 2007 12:38 PM

Performance Implications of try/catch/finally

The accepted wisdom regarding performance of try / catch | finally in C# has normally been: try has no performance side-effects unless an exception is thrown. A discussion I was involved in recently caused me to discover some performance implications...
Posted by PeterRitchie | 10 comment(s)
Filed under: , , ,