>>You beat me to the point that strong typing does prevent subtle bugs. If you are trying to do something that is inappropriate for one or more of the operands, you find out at compile time instead of run time.
>
>I just recently discovered the "resolve" feature, (OK, I'm slow!) where you can put your cursor on a squiggly line that the compiler is not liking and the IDE suggests ways to resolve the issue and when you select one, resolves it for you.
>
>Another big time saver.

PluralSight has a couple of terrific courses by Kate Gregory about VS tips and tricks. That is in one of them. Highly recommended. She is not their most famous presenter but she offers meat and potatoes advice a .NET developer can benefit from on a daily basis.