A year ago on this day, I wrote a blog post about the demise of
and issued a challenge for users of Open Source Software to contribute
to their favorite projects.
Microsoft just unveiled a new web
property intended to clarify its
position on Open Source as well as provide a one-stop location to find
out what Microsoft is doing in the Open Source space.
ELMAH, which stands for Error Logging Modules and Handlers for
ASP.NET, is an open source project which makes it easy to log and view
unhandled exceptions via its pluggable architecture.
One surefire way to sound really really smart is to invoke a law or
principle named after some long dead guy (an alive guy is acceptable
too, but lacks slightly in smart points).
Have you ever wanted to take a look at the internals of the .NET
Framework? Sure you can (and should) fire up
and see the Base Class Libraries, but what about the fully commented
source code? What about the parts implemented in C++?
When summer arrives, many like to create a new look via a haircut or new
threads. I prefer to change the look of my blog with a new design.
received an email today informing me that I’ve been awarded the status
of Microsoft MVP in the Visual Developer - ASP/ASP.NET category. I was
aiming for an MVP for non-visual developers, but my 57
didn’t have enough clout to make that happen.
Last year when all the hubbub surrounding
was happening, I tried to rally people around the idea of a Contribute
to Open Source day on July 26^th^.
Update: For an interesting counterpoint to the myth of the 10x engineer,
check out this blog post by
Shanley. My post is more
focused on what makes a good developer than the 10x myth.
2.0 is progressing nicely. The plug-in architecture is pretty much
feature complete. The code is still undergoing code review, testing, and
tweaking, but it is possible to start building plug-ins for it right
away with the understanding that some details might change.
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? ;)