The information in this article applies to:
SYMPTOMSAfter a Component Object Model (COM) client has loaded MSDev.exe using the COM automation interface, MSDev.exe does not automatically close when its last reference is released. RESOLUTIONUse Application.Quit method of MSDev.exe to cause it to remove itself from memory just before releasing the last reference to it. See the MORE INFORMATION section of this article for sample Visual C++ and Visual Basic code. STATUSThis behavior is by design. MORE INFORMATION
MSDev.exe is the Developer Studio shell. In Visual Studio 97 it hosts
Visual C++, Visual InterDev, Visual J++, and the InfoViewer. In Visual
Studio 6.0, it only hosts Visual C++. It supports an automation interface
that exposes its object model. An external application using the object
model can access internal functions to automate tasks such as building
projects, changing their settings, modifying text files, and so on.
This Visual Basic code illustrates the use of the Quit method:
REFERENCESFor additional information, please see the following article in the Microsoft Knowledge Base: Q192913 BUG: EnableModeless Causes Events to Fire LateFor more information on Automation and the Developer Studio object model, please see the following Help topics: Visual C++ 5.0 Online Help: Developer Products; Visual C++; Developer Studio Environment User's Guide; Automating Tasks in Developer Studio; Developer Studio Objects; Overview: Developer Studio Objects; Automating Developer Studio Tasks from Other Applications Additional query words:
Keywords : kbAutomation kbide kbVC500 kbVC600 kbVisID100 kbVJ100 kbVJ110 kbVS97 kbDevStudio kbVJ200 kbGrpDSTools kbvc600faq |
Last Reviewed: December 22, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |