Microsoft KB Archive/168411: Difference between revisions
(importing KB archive) |
m (Text replacement - """ to """) |
||
| Line 45: | Line 45: | ||
== SYMPTOMS == | == SYMPTOMS == | ||
When a Visual Studio 97 object model user applies a switch to a project and that switch is valid | When a Visual Studio 97 object model user applies a switch to a project and that switch is valid "per-file only" (such as the /h switch on MIDL), then Developer Studio does not return an error and the switch is not saved when the project is saved. | ||
</div> | </div> | ||
Latest revision as of 11:04, 21 July 2020
Article ID: 168411
Article Last Modified on 10/17/2003
APPLIES TO
- Microsoft Visual C++ 5.0 Enterprise Edition
- Microsoft Visual C++ 5.0 Professional Edition
This article was previously published under Q168411
SYMPTOMS
When a Visual Studio 97 object model user applies a switch to a project and that switch is valid "per-file only" (such as the /h switch on MIDL), then Developer Studio does not return an error and the switch is not saved when the project is saved.
RESOLUTION
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This problem was corrected in Microsoft Visual C++, version 6.0.
MORE INFORMATION
There is no facility in the Developer Studio 97 automation object model to add settings on a per-file basis. Some settings can only be applied at the file level. Therefore, some settings cannot be set through Developer Studio automation.
Visual Studio 6.0 supplies new Automation methods that provide this functionality.
REFERENCES
Visual Studio Online Documentation: search on the following methods of the Configuration object:
- AddFileSettings
- RemoveFileSettings
Keywords: kbbug kbfix kbide kbvc600fix KB168411
