ID: Q162039
The information in this article applies to:
The Visual J++ (VJ++) Debugger fails on subsequent debug sessions on a machine running Windows NT that has both Visual C++ (VC++) 4.2 Enterprise Edition and VJ++ 1.0 installed.
To workaround the problem, change the extension on the "Msdev\Bin\Ide\Msvcent.pkg" file before starting Microsoft Developer Studio to use VJ++. This disables the VC++ Enterprise Edition, but allows you to debug Java code.
NOTE: You need exit Microsoft Developer Studio, change the extension back to .pkg, and then restart Developer Studio in order to re-enable the VC++ 4.2 Enterprise Edition.
Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This problem has been fixed in Visual J++ 1.1.
On a machine that has VC++ Enterprise Edition (version 4.2), Internet Explorer version 3.0 and VJ++ version 1.0, do the following:
1. Create default JAVA applet using the Applet Wizard.
2. Press F5 once. The debugger loads fine.
3. Stop Debugging.
4. Press F5 again.
You will notice that Internet Explorer 3.0 loads up, Developer Studio reports that it is loading symbols and then nothing happens. Developer Studio does not put the Debug option on the menu bar, but all the menus are in Debug mode. If you attempt to, say, rebuild the applet, it informs you that doing so will stop the debugger.
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 : kbtool kbDebug kbide kbVJ
Version : 1.0
Platform : WINDOWS
Issue type : kbbug
Solution Type : kbfixLast Reviewed: November 12, 1998