Just the other day, I tried viewing a web application I’m developing on my local machine. After navigating to http://localhost/MyWebApp/ I got a blank browser screen. Nada. Zippo. Nothing. Not even the benefit of an error message.Read More
I just received the good news from one of my clients that they installed
Subversion over the weekend. We’ve all
been wrestling with using Microsoft Visual Source
CrapSafe over the
VPN (and yes, we tried out SourceOffSite which helped) but the sheer
number of problems we ran into was overwhelming.
Before I spend time writing my own, does anybody out there know of an ASP.NET custom control that can render a nice interface for specifying a connection string?Read More
The United States is like your family, it’s got its problems and can seem dysfunctional at times, but you gotta love it, and it sure beats being in some of them other countries.Read More
It’s an odd quirk of our taste for “round” numbers that we tend to celebrate milestones that are multiples of a power of ten. For example, a 10th anniversary is somehow more significant than a 6th anniversary. Likewise, a 100th post is more significant than a 73rd post.Read More
I’m not sure if this is common knowledge, but you can place template parameters in your SQL scripts and evaluate them within query analyzer. I think I learned this one a long time ago from a former fantastic SysAdmin, turned DBA, turned Developer, Tyler.Read More
You kind of get the feeling that Keith Brown has a beef with soap
exceptions when he writes that SoapException Sucks.
I won’t rehash everything he says here, but the gist of his complaint is that when throwing an exception from within a web service, the exception gets wrapped by a
SoapException. What’s so bad about that? As Keith relates, the
Message property of the
SoapException class intersperses your fault string with a load of other crap you really don’t care about. Also, the
InnerException doesn’t get serialized into the SOAP fault packet, so it is always null on the client side.