VC++ keeps asking to rebuild solution

Question

0.00/5 (No votes)

See more:

Hi All,
ok heres the problem Yesterday i started VC++ as usual and started work on my project long story short when ever i try to debug VC++ asks if
i want it to build all 4 projects as thay are out of date but i built the solution just before i hit the start debuging button :( , now ive got a backed up version from a day or 2 ago and that seams fine :) but i dont know what is wrong with it, i suspect that a some how the project solution has gotten messed up but donno how so can some one PLEASE tell me what went wrong so that i can sort this out.

Thanks in Advance :thumbsup:.

Posted 19-Jan-11 23:07pm

ryan20fun

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Andrew Brock · Accepted Answer · 2011-01-19T23:18:00

This is most likely a problem with your time stamps.
If you set your clock back (or got the files from someone in a different time zone) then the source files will have a newer time stamp than the compiled object files, hence Visual Studio thinks the source file has changed.

An annoying fix for this is to open every file and save it to update the time stamps.
Or, just put your clock back if you changed it ;P

dasblinkenlight · Accepted Answer · 2011-01-19T23:21:00

Solution 2

One of the source files, or perhaps a common header, may have a modification timestamp in the future. This happened to me once when I was debugging on a night when the computer clock was automatically set 1 hr back at the end of the daylight saving time period, so one of my source files appeared to have been modified in the future.

Posted 19-Jan-11 23:21pm

dasblinkenlight

Comments

Andrew Brock 20-Jan-11 5:23am

OMG, that totally happened to me too. Thats how I know :D

dasblinkenlight 20-Jan-11 5:38am

Nice! BTW, I think the fact that it is happening on DST nights indicates that there's a logical bug in the OS: the modification time of a file is set to the local time, not a UTC time + offset.