A pity VS out of date issue

最新推荐文章于 2025-09-10 15:16:07 发布

转载最新推荐文章于 2025-09-10 15:16:07 发布 · 75 阅读

0 ·

CC 4.0 BY-SA版权

原文链接：http://www.cnblogs.com/taoxu0903/archive/2010/10/29/1864552.html

文章标签：

#c/c++

本文解决了一个在Visual Studio 2010中C++/CLI项目遇到的编译问题，表现为每次成功构建后运行时提示过期。通过DebugView和深入研究发现pdb文件的时间戳异常，而其他版本的VS未出现此问题。

I met a VS out-of-date compiling issue. The situation is:

1. It appear all the time if compiling a VS2010 C++/CLI project. After a successful build, press F5 to run it, prompt me: out of date! after using debugview for further research, the result is: everytime VS finds the exe is in first modified time (it's correct) while the pdb modified date is always wrong from its real date displayed in explorer. Googled, but no result...

2. It doesn't reproduce for VS2008 and VS2010 other languages.

3. It should relate to the random compile error if compiling targeting to dotNet 4.0 for the vc project: "error: not valid win32 fileTime". BUT I can't figure out the reason..

By diagnosticing a VS out-of-date issue, whatever, I gained something:

1. FileTime stored by NTFS VS FAT. There is a FileTime stored in file system. MSDN gives good example to help understand it:

A file time is a 64-bit value that represents the number of 100-nanosecond intervals that have elapsed since 12:00 A.M. January 1, 1601 Coordinated Universal Time (UTC). The system records file times when applications create, access, and write to files.

The NTFS file system stores time values in UTC format, so they are not affected by changes in time zone or daylight saving time. The FAT file system stores time values based on the local time of the computer. For example, a file that is saved at 3:00pm PST in Washington is seen as 6:00pm EST in New York on an NTFS volume, but it is seen as 3:00pm EST in New York on a FAT volume.

2. DebugView + devenv.exe.config: to trace down issue: Enable C++ project system logging

Note: open debugview firstly and then open VS.

转载于:https://www.cnblogs.com/taoxu0903/archive/2010/10/29/1864552.html