Re: Dependency .CPP --> .OBJ broken
- From: "Doug Forster" <doug_ZAPTHIS_AT_ZAPTHIS_TONIQ_DOT_CO_DOT_NZ>
- Date: Tue, 20 Jun 2006 11:49:39 +1200
Which version of VS are YOU using. I'm using VS2005 with a very similar
sounding story to yours and the OP's except mine is happening to a C#
solution. Again mine was working perfectly a couple of weeks ago and Rebuild
all or Clean works fine. I also use Zone Alarm if that could possibly be
relevant. I have been presuming that the problem might have something to do
with MSBUILD but I don't understand enough about that tool to troubleshoot
it and since it is part of the .NET framework I don't even know how to check
for changes.
Cheers
Doug Forster
"chanceu" <chanceu@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AE7539A3-7545-4E20-B470-4ACD95A44F9C@xxxxxxxxxxxxxxxx
What version of Visual Studio are you using?
I am seeing a similar problem, but mine only seems to appear when
compiling
.C files. I have a dialog project that is a standard VC++ dialog project
with
.CPP files, but I included a .C file from another project for a variable
declaration.
If I modify a .CPP file , it compiles and links without a problem. If I
try
to build again, there is no compile or link as everything is up to date,
which is how it should behave.
If I modify the .C file, it APPEARS to compile and link, but the object
never gets updated. If I try to build again, it again appears to compile
and
link and again never updates the object. If I delete the object for the .C
file and build, the object gets created and everything works fine, but if
I
modify the .C file again, the problem shows up again. As you have seen, if
I
do a "Rebuild All", everything gets built correctly, but all that really
does
is delete all the output files before compiling and linking.
What updates have you performed lately? I have updated 3 things over the
last week and I know it was working properly prior to that, but I cannot
say
that any of the updates are causing the problem. My updates were all the
recent Windows XP security patches, all the recent Office security
patches,
and a ZoneAlarm program update. I don't think ZoneAlarm has anything to do
with it since .CPP files work and it works if I delete the object. I'm
really
wondering if one of the Office updates is causing a problem with one of
the
databases VS uses.
Chance
.
- References:
- Dependency .CPP --> .OBJ broken
- From: unoriginal_username
- Dependency .CPP --> .OBJ broken
- Prev by Date: VS2005: editing while debugging
- Next by Date: Visual J# Redistributable Package ????
- Previous by thread: Dependency .CPP --> .OBJ broken
- Next by thread: Re: Dependency .CPP --> .OBJ broken
- Index(es):
Relevant Pages
|