Coding Standard for .NET and VB6 Teams
I started my new job at PRG/Schultz last week here in Atlanta, and had a very nice first week. One of my first tasks is to create a coding standard for all new .NET development. Now anyone that reads the MSDN docs should know what Microsoft recommends. There are also others besides Microsoft that have adopted this new coding style. There is even an automated compliance checker called FxCop available from Microsoft. Most all .NET books and articles are also written to this new standard, checked by FxCop. So it seems obvious that the Microsoft recommendation should certainly be the first choice. Especially when you consider large corporations assume that people will come and go over time.
So what's my point then? The existing team here at PRG is used to the traditional Hungarian style used in most VB6 shops. I don't want to disrupt things too much, so I would really appreciate your feedback on this one. What types of experiences have others out there had moving a team to the new standards? What would you recommend to help them understand the need and reach of this new style? Also, is anyone out there actually not adopting the new .NET standards, and why is that? The more feedback the better, so don't hold back -- send stories, links, etc. By the way, this is going to be a VB.NET shop, so any thoughts on customizing the standards towards VB.NET will be appreciated.