A few people mentioned that they had the following compiler error when
trying to compile
Testing code written for the web is challenging. Especially code that makes use of the ASP.NET intrinsic objects such as the
HttpRequest object. My goal is to make testing such code easier.
What would you do if you found out that a project you were working on
was going to be used in an unethical or illegal manner?
One praiseworthy aspect of ASP.NET 2.0 is its much improved XHTML
compliance. However, there is one particular implementation detail
related to this that causes some web designs to break and could
have been implemented in a better manner.
With Father’s Day fast approaching (June 17 this year), and now that I
have joined the hallowed ranks of fathers, I thought I’d have a little
fun writing about something I posted on my blog two years
but has recently popped up on my radar.
Most of the time when I’m testing my code, I only test it using the
en-US culture since, …well…, I speak English and I live in the
U.S. Isn’t the U.S. the only country that matters anyway? ;)
Update: I’ve created a new NuGet
for Subkismet (Package Id is “subkismet”) which will make it much easier
to include this in your own projects.
A while back I mentioned the beginning of phase 1 of my total world
This morning at 3:55 AM, phase 1 is officially complete with the birth
of our son, Cody Yokoyama Haack, all seven pounds and fourteen ounces of
thing that never gets old is when someone visits me and asks to
check some email on my computer.
Microsoft recently released Windows Live Writer Beta
2, the long awaited next
version of their blog editing tool. Although there are a few
with WLW, I find the user interface and usability to be really nice.
They make great use of the right sidebar panel.
I don’t know about you, but every company I’ve ever worked at had a Fort
Knox like system in place for deploying code to the production server.
Typically, deployment looks something like this (some with more steps,
some with less):
Ok, this will be my last post on Twitter for the time being. My last
on the subject pointed out flaws with it, so I thought I’d follow up
with something positive.
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