BUG: Changes to Remote Project Files Not Detected

Last reviewed: July 31, 1997
Article ID: Q145995
The information in this article applies to:
  • Microsoft Visual C++, 32-bit Edition, versions 4.0, 4.1, 4.2, 5.0 for the following platform: - Windows 95

SYMPTOMS

Developer Studio does not detect changes to project files located on remote computers when those project files are modified by an external source on a remote computer. This occurs when Developer Studio is running on Windows 95. It may also occur on Windows NT when the remote files are on network servers that are not running Windows.

There are two ways this problem manifests:

  1. If a remote file is open in Developer Studio and is modified by an external source, Developer Studio should notify the user that the file has been changed outside of the source editor and prompt the user to reload the file. However, there is no notification.

  2. If a remote file is modified by an external source on a remote computer and a build is launched, Developer Studio does not detect it. It will not recompile the file or do whatever build step is necessary to rebuild files that are dependent on the remote file.

CAUSE

The problem occurs on networked systems that do not support the file change notification functions defined in the Win32 API.

RESOLUTION

To work around problem 1, you need to reload the file manually.

To work around problem 2, you need to do a Rebuild All of the project, rather than a Build.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words: modify update dependency
Keywords : vcbuglist400 vcbuglist500 VwbIss kbusage
Version : 4.0 4.1 4.2 5.0
Platform : Win95
Issue type : kbbug


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 31, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.