By "finer granularity" I meant only that you could build more frequently. For example if currently you build at (say) midnight each day after everybody has finished work, then if Module "X" was changed 3 times and now fails to compile you've got to figure out which change caused it to fail. If, however, you'd done several builds during the day (e.g. every 2 hours) then you have more chance of discovering a broken build for which only one checkin has been done.
Taking this to an extreme you end up with CI = Continuous Integration in which typically there'll be a gate on the checkin process with some mandatory regression tests needing to be passed before checkin can be done. There are lots of ways to implement this in practice: you could allow checkin but advance a stable label only as each checkin is built and validated. In the ideal world CI should ensure that your code always builds. However this is a big topic which is why I suggested only a small change to your existing process rather than a fundamental change of strategy.
You're first going to have to describe what you mean by "autocorrect". If you're talking about a spell check (which is what I think of when I hear "autocorrect") there's no such thing in Visual Studio.
Visual Studio has Intellisense, which will suggest names of existing objects in your code to make things easier and faster to type.
you don't get it. as far as i remember, in VS 2008 / 2015 when i type, for example, "Move" and the suggestion will pop up (like Moveblablabla, etc) BUT if i continuing type "(" (WITHOUT have to press Esc) it will become:
Moveblablabla() //this is when i say, it force you use its suggestion
Oh I get it. I've understood for a while now. Every version of VS with Intellisense has behaved the way you're describing, though, each language editor has it's options set differently from the others by default.
I already told you what you're going to have to do. Tools/Options/Text Editor/... and start exploring the options.