Article ID: 835516 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
In the Microsoft Visual Studio .NET 2003 IDE, if you add a method to an interface in a Microsoft Foundation Classes (MFC) project with ATL support while the project is checked in to Microsoft Visual SourceSafe, you may receive a prompt to check out unnecessary files in addition to the files that you modified when you added the method.
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 Visual Studio .NET 2003 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:
http://support.microsoft.com/contactus/?ws=supportNote 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 ----------------------------------------------------- 28-Jan-2004 11:03 7.10.4027.0 1,850,368 Vcpkg.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
Article ID: 835516 - Last Review: January 17, 2015 - Revision: 1.6