Speed is fine here and I generally enjoy working with VS 10 when I'm on Windows (showing errors while typing is a fantastic feature which I haven's seen for c++ before VS10). But my annoying VS 10 bug is that approximately once per week it simply refuses rebuilding a changed c++ file until I clean and rebuild the whole project. It just continues using the old object file despite having c++ files with a newer date - and what makes this really annoying is that this is a bug you certainly only notice after a while when results just stop making sense. Others in the project have the same trouble - maybe we messed up some setting, but we haven't found any setting yet about simply ignoring source-changes...
Try adding a semicolon in your source files immediately after your includes:
#include "stdio.h"
#include "system.h"
;
int StartOfYourCPPCode()
{
There's a long-standing bug with pre-compiled headers and code regeneration that (apparently) Microsoft has never fixed. There were (still are?) so many obscure issues with PCH that I just disabled it altogether.
Thanks. We also had suspected pre-compiled headers and also just disabled them completely, but unfortunately that wasn't it. I'll try adding a semicolon next time it happens to check if that changes something.
