I don’t know about you, but I find it a pain to call stored procedures
from code. Either I end up writing way too much code to specify each
SqlParameter explicitly, or I use a tool like Microsoft’s Data Access
SqlHelper classj to pass in the parameter values,
which requires me to remember the correct parameter order (it actually
supports both methods of calling a stored procedure). What a pain!
In a recent post,
I compared the expressiveness of the Ruby style of writing code to the
current C# style of writing code. I then went on and demonstrated one
approach to achieving something close to Ruby’s expressiveness using
Extension Methods in C# 3.0.
Are your unit tests a little flat lately? Have they lost their shine and
seem a bit directionless? Maybe it’s time to jazz ’em up a bit with the
latest release of
Come on people! I count on you to keep me informed! It looks like he
started it way back in March.
UPDATE: Looks like Ian
Cooper had posted
pretty much the same code in the
to Scott’s blog post. I hadn’t noticed it. He didn’t have a chance to
compile it, so consider this post a validation of your example Ian! :)
You know what I really like about posts like
It’s a lot less writing for me. When people ask me what principles
Subtext development tries to follow I can just point them to this post
by Patrick Cauldwell.
This just in. CodePlex is planning to roll out TortoiseSVN support!
I wrote about
on my company’s blog, but thought I’d mention it here since I assume not
everyone has jumped at the chance to subscribe to that
blog (go on, it won’t bite)
Scott Hanselman writes a thought provoking post that asks the question, Is Microsoft Losing the Alpha Geeks? An
interesting question, but troublesome to make sense of, let alone answer.