Ken Brubaker

The ClavèCoder

<December 2008>
SuMoTuWeThFrSa
30123456
78910111213
14151617181920
21222324252627
28293031123
45678910


Navigation

Subscriptions

News

Kenneth Brubaker
Senior Application Architect

Locations of visitors to this page

Post Categories



Tuesday, May 18, 2004 - Posts

Debugging: How to debug your app that crashed in the field (Post-mortem debugging)

When an app crashes in XP, an mdmp (mini-dump) file is created can can be used to debug the beast. This codeproject article says how.

A copy is sent to Microsoft by default. You can also get a copy off the hard drive. Here's more info. Chris Sells also has a posting that explains how you can sign up to get the copies that ship to Microsoft.

posted Tuesday, May 18, 2004 5:51 PM by kenbrubaker with 0 Comments

Coding Standard: Enums standards, fresh and crispy

Brad Abrams clued us in to the revised Enum usage guidelines from the blog of Krzysztof Cwalina. With annotations, no less!

Brad attributes the legwork to Kit George who posts on the BCLTeam blog.

The entry include expanded instructions on the zero value and on versioning. Don't burn your fingers!

posted Tuesday, May 18, 2004 9:59 AM by kenbrubaker with 0 Comments

VS2005: My, My. Two posts on the My... namespace

Here are two interesting posts on the My namespace. It's interesting to consider the “My” namespace as just another utility library that every enterprise builds on top of the FCL.

By 3Leaf.

By Simon Stewart (MVP).

posted Tuesday, May 18, 2004 4:06 AM by kenbrubaker with 0 Comments

XML: Why .NET 2.0 supports XQuery 1.0 and not XPath 2.0 or XSLT 2.0

I missed an important post that Dare Obasanjo, the .NET XML lead, made a couple of days ago, where explains why they will only support XQuery 1.0 in .NET 2.0. The key quote:

XQuery with its FLWOR construct and user defined functions fits more naturally with how both programmers and database administrators access and manipulate data than does XSLT 2.0. Thus we feel XQuery and not XSLT is the future of XML based query and transformation. 

This doesn't mean that we will be removing XSLT 1.0 or XPath 1.0 support from the .NET Framework. It just means that our innovation and development efforts will be focused around XQuery going forward. 

A must read.

posted Tuesday, May 18, 2004 3:15 AM by kenbrubaker with 0 Comments




Powered by Dot Net Junkies, by Telligent Systems