Here's a great link to Microsoft Internal Coding Guidelines (.net & c# in particular). more...
These coding guidelines are pretty close to what I do generally, with the exceptions that I prefix member variables with an _ (underscore). The guidelines say to just use the this. (or me. in VB) prefix when using the variable to diferentiate it from a local variable "if you want to".
I've seen way too many bugs come from someone accidentally hiding a member variable with a local variable, and the 'optional' this. prefix doesn't reduce the chance of that happening enough to be comfortable with it.
On the other hand I'm a contractor, and try to stay used to the most standard things I can. For instance I don't customise the layout of Visual Studio. This means I get used to working with a set-up that I can get anywhere and everywhere. When you need to be able to move around from job to job, I think that's a valuable benefit. You can sit me infront of a new PC with a fresh VS installation and I can hit the ground running. I've seen people take a week getting a machine set-up, installing all the add-ins they need and rejigging the windows to be 'just so'. That's a week that I'm not comfortable billing for!
So I see coding standards in the same light. Everyone who has some has their own, but if I can code with the same style / standards as the libraries that everyone's using, then at worst my stuff shouldn't be abhorrent :)