VS2005, C/C++.
I would think it looks at the date/time of the .obj file to see if it's
older than the .c/.cpp file and build it if so (which is where making the
.obj match the source file option would be beneficial). The .c file may be
dated 5 days ago, I build today where a header was updated, .obj file gets
today's date. I download changed .c file from source control dated 2 days
ago, I build but it doesn't see the change (presumably because .obj is
newer).
> Hello David,
>
[quoted text clipped - 35 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
Steven Cheng[MSFT] - 08 Mar 2007 12:18 GMT
Thanks for your reply David,
I have discussed this with some other engineers. And based on our analysis,
the visual studio's behavior is as expected, and there should have an
setting in the source control tool to control the check in behavior of a
certain module in current project.
Are you using VSS or any other source control tool? If VSS, this issue is
most likely caused by your VSS client setting date/time on local files as
¡°Check In¡± or ¡°Modification¡±. Please change it to Current via the
following:
Open Visual SourceSafe;
select Tools-->click Options-->switch to the "Local Files" tab
set the value of "Set date/time on local files" as Current.
After that, retrieve the files again then you can build your application.
If your source control is not VSS, you may check if it has the similar
functions; if it has not, you may need to manually modify the obj file date
to an older date than your source files. Some third party software may help
you change the date.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
David F. - 08 Mar 2007 21:12 GMT
The source control I use has that option, but I want the source file to be
download as the date/time it changed and not the date I'm downloading it so
I'm simply looking for the option in VS2005 that will give an "option" of
building the .obj file using the date/time of the source files. That would
give me the flexibility to do it the way I think it should work (and the way
other compilers work) and having it an option would allow others to continue
doing it as it does now by default.
> Thanks for your reply David,
>
[quoted text clipped - 32 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
Steven Cheng[MSFT] - 12 Mar 2007 13:24 GMT
Thanks for your reply David,
For the Visual Studio's behavior, it is building output as expected.
regardless of whether Visual studio setting, have you tried setting the
source control's option as I mentioned in the last reply to see whether the
changed behavior(output) is what you expect? So far, based on some further
discussing with other engineers , they think this issue is more likely to
get overcome through the source control tool's setting, otherwise, you may
need to manually change the obj file's version.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
David F. - 20 Apr 2007 18:20 GMT
The difference is, I pull from source control to a local drive where the VS
project uses those local files and doesn't look in source control itself.
> Thanks for your reply David,
>
[quoted text clipped - 15 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.