Hi Bern,
Sorry for letting you wait.
I performed some review to the attached text file. Below is some
interesting output:
Invoking LINK.EXE:
-out:o:\out\1\Mstn\Bentley\MicroStation\ustation.dl l -assemblydebug -WX
-OPT:NoWin98 -OPT:NOREF -OPT:NOICF -Ignore:4087 -Ignore:4089
-incremental:yes -fixed:no @o:\out\1\Mstn\build\mscore\core\link.rsp
/incremental:no
/nologo
/fullbuild
LINK : file alignment: 512, section alignment: 4096
I see /incremental being overridden with/incremental:No.
I am sure you have gone through
http://msdn2.microsoft.com/en-us/lib...yf(VS.80).aspx
Can you double check on the following list:
LINK performs a full link if any of the following situations occur:
¡¤ The incremental status (.ilk) file is missing. (LINK creates a
new .ilk file in preparation for subsequent incremental linking.)
¡¤ There is no write permission for the .ilk file. (LINK ignores
the .ilk file and links nonincrementally.)
¡¤ The .exe or .dll output file is missing.
¡¤ The timestamp of the .ilk, .exe, or .dll is changed.
¡¤ A LINK option is changed. Most LINK options, when changed
between builds, cause a full link.
¡¤ An object (.obj) file is added or omitted.
¡¤ An object that was compiled with the /Yu /Z7 option is changed.
I am suspecting write permission. Can you confirm this point? Thanks. Also,
you may use Process Monitor or FileMon from
www.sysinternals.com to check
if you got any file access deny error during the compilation.
Finally, I am not sure if is it possible for you to reproduce this problem
in a little sample project? If so, please feel free to send it to me. It
will make the analysis and troubleshooting more accurate.
I will wait for your further feedback, thanks.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.