I agree w/ Anton. You need their buy-in, else the coding standards are just arbitrary rules meant to inconvenience them (at best) or stifle their creativity (at worst).
I also recommend making the coding standards concise, and, for the most part, tell your devs what they shouldn't do rather than providing an exhaustive list of what they should do. Find stuff that they'd reasonably agree on (like "avoid using empty catch blocks like the plague, as they just mask errors"). Make it known that they are the beneficiaries of the dev standards to achieve buy-in from the majority.
Rushing to fire non-pliable employees isn't the answer. Turn this into a positive experience for your devs and everyone wins.
