You are currently offline, waiting for your internet to reconnect

FIX: Changes to a bitmap resource are lost when the bitmap location is moved to a different folder in a Visual C# .NET solution

This article has been archived. It is offered "as is" and will no longer be updated.
When a bitmap resource is modified and is moved to a different folder in a Microsoft Visual C# .NET solution without saving the bitmap first, the changes that are made to the bitmap resource are lost. If the solution is closed and then reopened, two bitmap resources are present. One bitmap resource is in the original location and the other bitmap resource is in the folder where the bitmap was moved.
This problem occurs because Microsoft Visual Studio .NET performs a copy operation instead of performing a move operation to move the bitmap to the new location. This problem only occurs when changes are made to the bitmap and it is moved before the changes are saved.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version      Size       File name   -------------------------------------------------------   31-Oct-2003  18:42  7.10.3303.0  2,172,416  Resedit.dll
To work around this problem, save changes to a bitmap resource before you move it.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.

Steps to reproduce the problem

  1. In Visual Studio .NET, create a new Microsoft Visual C# .NET Windows Application.
  2. In Solution Explorer, right-click the project, point to Add, and then click New Folder.
  3. Right-click the project, point to Add, and then click New Item.
  4. In the Add New Item dialog box, click Bitmap File.
  5. Edit the bitmap image.
  6. Move the bitmap to the folder that was created in step 2.
  7. Open the bitmap resource. Notice that the changes that were made in step 5 are not saved..
  8. Close and then reopen the solution. Two bitmap resources will appear. One bitmap will be located under the folder that you created in step 2 and the other bitmap will be located under the project root.
The problem can be prevented by saving the bitmap resource after step 5 and before step 6.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the Standard Terminology That Is Used to Describe Microsoft Software Updates

Article ID: 831536 - Last Review: 01/17/2015 05:28:19 - Revision: 1.4

Microsoft Visual Studio .NET 2003 Enterprise Architect, Microsoft Visual Studio .NET 2003 Enterprise Developer, Microsoft Visual Studio .NET 2003 Professional Edition

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbfix kbbug kbqfe KB831536