BUG: Default Beep When Editing Read-Only Files

• Microsoft Visual InterDev, version 6.0

SYMPTOMS

When a user makes changes to a read-only file that is not under source control, a default beep sound is made by the system.

CAUSE

This behavior is an intentional warning that the user is editing a read- only file without first getting a working copy.

RESOLUTION

To prevent the sound, get a working copy of the file before attempting to edit it.

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.

MORE INFORMATION

Different behavior occurs in files that are under source control. When making changes to a read-only file that is under source control, a dialog box appears offering to check out the file before the change is allowed. If you decline to check out the file, you will not be allowed to edit it.

From the Tools menu, select Options. Using the Projects / Web Projects portion of the Options dialog box, users can select the option to Get a Write-Enabled copy of each file whenever opening it. Selecting this option will make it easier to prevent editing of read only files.

Steps to Reproduce Behavior

1. Double-click a file from the Project Explorer.



2. Click the Open Read Only button from the Open File dialog box that appears.



3. Begin typing in the file after it has finished opening.

Additional query words:

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