I came across this interesting free white paper, C#/VB .NET Coding Guidelines from Iridium Software. To download it you simply need to register with an email address. Whilst I don't agree with everything in it, e.g.
Remove the Visual Basic reference from your project. Making use of the original Visual Basic functions has been proven to be up to 1000 times slower than the .NET counterparts; you have been warned.
We advise completely the opposite at vbCity as it appears to be FUD and urban legend rather than proven
and
There has been an urban myth in programming academia that short procedures of no more than “a page” (whatever that is) are better. Actual research has shown that this is simply not true. There have been several studies that suggest the exact opposite.
Although I don't dispute the findings of any report I suggest that any findings are generic and that something like this actually depends a lot on the individual developer. For me, procedures much larger than 1 page don't work.
However, what I do like about the document is that it offers guidelines not rules and 95% appears good common sense to me. Steve Sartain has come up with a very readable document that offers comprehensive guidelines for structuring code writing. Most of what he says I shall take on board. Certainly if you find you have an hour or so free you could do worse than read his white paper.