BUG: Files Modified Outside of VI Do Not Get Copied to Server

ID: Q190748

The information in this article applies to:

SYMPTOMS

When opening or creating a Visual InterDev Project, you may encounter the following warning:

The project file 'project file' is on a drive which does not support file changes.
Files modified in editors external to Visual InterDev will not be saved to the master Web until you close the project."
In master mode, if you open a file in an external editor (using the Open With command) and save your changes, those changes will not be copied to the master web until you close the project, or use the "Release Working Copy/Check In" commands, which explicitly update the master web.

In local mode, link information will not be parsed and updated in the working web when you save your changes. This means that link view may show incorrect or outdated link information.


CAUSE

Visual InterDev relies on being notified by the operating system when a file has changed outside Visual Studio in order to copy the changed file to the master web (or cause a reparse of the file in the local working web).

Typically, this warning occurs only when opening/creating a project on a drive that is mapped to another computer. Note that it is only certain mapped drives that exhibit this behavior.


RESOLUTION

The workaround is to create the project on the local hard drive instead of a mapped drive.


STATUS

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

Additional query words: 


Keywords          : kbide kbVisID600bug kbGrpASP 
Version           : WINDOWS:6.0
Platform          : WINDOWS 
Issue type        : kbbug

Last Reviewed: May 20, 1999