"=?Utf-8?B?SmFtZXMgRWR3YXJkcw==?="
<JamesEdwards@discussions.microsoft.com> wrote in
news:046AFA3C-C3A1-4320-95B9-5F7BA27E5248@microsoft.com:
> I'm trying speed up our build by creating a new file
> "composite_file.cpp", which is simply
[quoted text clipped - 11 lines]
> stopped working. When I modify "file1.cpp", VS.NET 2003 does
> not rebuild "composite_file.cpp" when I do a "build solution".
This should work. I tried this with a simple MFC application and I
could not reproduce this bug. Can you reproduce this with a
simple application and share the steps?
> Where are the VS.NET header dependencies stored for a .sln file,
> and how can I view/add to them or force them to be regenerated?
> I'm suspecting the .ncb file.
It's the .idb files. You cannot really view/add to them. You can
delete them and the compiler will regenerate them.
> We're not using precompiled headers because I've found they
> introduce hard-to-solve bugs that magically disappear when you
> dont use them.
What bugs are you hitting?
Thanks,

Signature
Tarek Madkour, Visual C++ Team
This posting is provided "AS IS" with no warranties, and confers
no rights.