I have read and it is stated that true Test Driven Development requires you write a test before creating objects or anything. So you basically write the syntax with what you expect to be the way it will be done in runtime. So I create a new unit test, and start typing:
MyNewObject obj1 = MyNewObject.Create();
Now as you will know, Visual Studio will be confused to hell with this and start to try and complete your statements for you. This is good, don't get me wrong, but fro times such as this when the syntax you are creating does not actually exist yet, it becomes quite tedious, so immediately i thought about SETTINGS, and there is a way to stop this. Check below (Completion Lists : Un-tick the main one and the two sub points, and this still leaves Ctrl + Space for auto complete functioning):
Cheers,
Andrew