I agree, coding guidelines are great, especially as a project gets large, and everyone thinks they've got the best way of doing things.

Naming is a tough thing to change, and the topic where compromise has to happen. I like Brad's naming conventions, he is a bit whitespace happy (ok, I'll stop now before I can't stop) but I think it would be better to keep an existing project consistent, rather than try to redo it all. When I dig into someone else's source code, the most important thing is that the naming is consistent within the project.

Whitespace is the thing I am most picky about, fortunately it is the easiest to fix. astyle (http://astyle.sourceforge.net/) can rearrange code to layout exactly how you like it. (It does support C# code, its just not advertised on the main project page). astyle comes with most Linux distros and Cygwin.

I have long thought about an on-checkin hook for revision control that reformats your code to some standard, so you can edit however feels comfortable without worrying about any standard. This would not only make everyone happy, it would keep your style self-consistent :) and make diffs more effective.

Yeah, Casey. I've thought about that kind of thing as well. Especially since the new VS.net is so customizable in that respect. The only issue would be that any file you opened would appear to have been edited...alot. And diffs with the working copy would be difficult to decipher. Perhaps a client-side mechanism could do the normalizing, although that wouldn't protect the repository. I'm just rambling now.

This is why I use temp1 convention for naming variables, class, and so on. That way I always have consistancy and built in obsfucation.