Take your side. State your case. Learn the reality.

new Guid() creates a 32-character GUID as a string. You can actually shorten that to 22 characters. Check out this post for the how-to!

Extending Mads Kristensens "shorter and URL friendly GUID"

There is only one commandment in the Gospel of the GUID: Thou shalt always use a GUID to uniquely identify a row in a table.

This is not rocket science, but it's a nice and handy macro for Visual Studio that generates a new GUID and inserts at the cursor location in the editor. No more running guidgen.exe, switching windows, copying to clipboard and pasting.

Here is a function I try to keep handy which tests a string for a Guid and returns True or False.

I wanted to use GUIDs for a specific table's primary key, but I had no intention of running two queries just so I could get the newly created row's GUID. Here's a great way to get data created within a stored procedure back to the code that called it.

Certain Data Architects (Dratz!) will tell you that GUIDs are for miscreants, deviants and DB n00bz. Well, I'm inclined to disagree with that generalization and lay out when GUIDs make perfect sense, when they're improper and why people who use Identity (auto-incrementing) columns shouldn't be allow...

Naturals? Idents? GUIDs? Oh, jeez. Getting an official opinion on which to use is about as hard as getting a lawyer to tell you exactly when its okay to shoot somebody. NOBODY wants to give you a straight up answer. And you can understand why; there are many different things you have to consid...

Microsoft realized they were on thin ice by removing the feature, so they made a wise decision in Service Pack 1 for Visual Studio 2005.