Article ID: 173164
Article Last Modified on 9/1/2005
APPLIES TO
- Microsoft Visual C++ 5.0 Enterprise Edition
- Microsoft Visual C++ 6.0 Enterprise Edition
- Microsoft Visual C++ 5.0 Professional Edition
- Microsoft Visual C++ 6.0 Professional Edition
- Microsoft Visual C++ 6.0 Standard Edition
This article was previously published under Q173164
SYMPTOMS
Developer Studio may appear to hang for 60 seconds or more when loading a workspace.
MORE INFORMATION
Following are several known causes:
- You may have many nodes expanded in InfoView.
After loading the class information for a workspace, Developer Studio restores the state of the InfoView pane to when you last saved the workspace. The more nodes that are expanded in InfoView, the longer it takes to restore the state. For optimal load time, collapse all of the nodes in InfoView, then save the workspace.
This is not an issue in Visual C++, version 6.0, because HTML Help is used for the Help engine rather than InfoView. - You may have a corrupted workspace options file.
The workspace options file will have the same base name as your project with a .OPT extension. This file does not contain the file lists or the build options needed to successfully build your projects. You may safely delete this file. If you find that you need to delete this file frequently, run a disk analysis tool such as ScanDisk to test the surface of your disk for bad sectors. You may have network or CD drive paths in your environment, Developer Studio options, or project settings.
Windows NT
To edit paths from your environment in Windows NT, follow these steps:
- In Control Panel, open System.
- Click the Environment tab.
Notice that the following two lists of environment variables exist:- System Variables
- User Variables
Windows 2000, Windows XP, and Windows Server 2003
To edit paths from your environment in Windows XP, follow these steps:
- In Control Panel, open System.
- On the Advanced tab, click Environment Variables.
Note that the following two lists of environment variables exist:- System variables
- User variables for UserName
Windows 95
To edit paths from your environment in Windows 95, use a text editor and open the C:\autoexec.bat file.
The environment variables you are most interested in are PATH, INCLUDE, and LIB. These contain the executable, include file, and library search paths respectively.
Remove all paths that point to locations on your network or your CD-ROM drive.Developer Studio options
To edit paths in your Developer Studio options, from the Tools menu, select Options. Select the Directories tab. In the "Show directories for" list, cycle through each of the four sets of paths--executable, include, library, and source--and remove all paths that point to locations on your network or your CD-ROM drive.
Project settings
To edit the paths in your project settings, from the Project menu, choose Settings. Select the C++ tab. Select "Preprocessor" from the Category drop- down list. Under "Additional include directories," remove all paths that point to locations on your network or your CD-ROM drive. Select the Link tab. Select "Input" from the Category drop-down list. Under "Additional include directories," remove all paths that point to locations on your network or your CD-ROM drive.
Save your projects and try again. If the problem persists, it may be that you created a new configuration based on a configuration that did have an include or library search path in the project settings that pointed to a location on your network or your CD-ROM drive. In this case, Developer Studio saves the options that the configuration was created with so that if you choose to click the Reset button on the Project Settings dialog box, the project settings will be reset to the options with which the configuration was created. Use one of the following methods to modify this configuration:- Delete all such configurations and recreate them.
- Use a text editor to modify the project file (.DSP) directly. This option is dangerous and may render the project file unusable in certain circumstances.
- The size of the .NCB is dependent on the number and size of your classes. It is regenerated when you open your workspace. You may delete this file and see if there is any improvement in load time.
Keywords: kbtshoot kbperformance kbprb KB173164
