FIX: Msdev.exe Fails when Component Inserted into VC++ Project

Last reviewed: January 22, 1998
Article ID: Q156918
The information in this article applies to:
  • Microsoft Visual J++ 1.0

SYMPTOMS

Microsoft Developer Studio, Msdev.exe, fails when attempting to insert a component into a Visual C++ project that is loaded into a Visual J++ only installation.

WORKAROUND

Do not attempt to insert a component into a Visual C++ project loaded in a Visual J++ only installation of Developer Studio. You must first install Visual C++ before trying to work with any Visual C++ project.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This problem has been fixed in Visual J++ 1.1.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Open an existing Visual C++ project in a Visual J++ only installation
2. Click OK in the dialog box warning that you do not have the build tools
   for that platform type.
3. On the Insert menu, click Component. 4. Select and Insert a new OLE Control to your project.

REFERENCES

For the latest Knowledge Base articles and other support information on Visual J++ and the SDK for Java, see the following page on the Microsoft Technical Support site:

http://support.microsoft.com/support/visualj/ http://support.microsoft.com/support/java/

Keywords          : VJGenIss
Technology        : kbInetDev
Version           : 1.0
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbfix


================================================================================


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: January 22, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.