Visual Studio 2005 appears to stop responding for up to 30 seconds (916450)
The information in this article applies to:
- Microsoft Visual Studio 2005 Express Edition
- Microsoft Visual Studio 2005 Professional Edition
- Microsoft Visual Studio 2005 Standard Edition
- Microsoft Visual Studio 2005 Team System Architect Edition
- Microsoft Visual Studio 2005 Team System Developer Edition
- Microsoft Visual Studio 2005 Team System Team Foundation:
- Microsoft Visual Studio 2005 Team System Test Edition
SYMPTOMSConsider the following scenario: - You are using
Microsoft Visual Studio 2005 in Design view to work with a Microsoft ASP.NET server control.
- The ASP.NET server
control contains many child Web controls that use resource information. The child Web controls may include controls that have been converted to
template controls and controls for which you have generated local
resources.
In this scenario, Visual Studio 2005 appears to stop
responding for up to 30 seconds. CAUSEThis problem is caused by the way that Visual Studio
2005 retrieves resource information for Web controls. Visual Studio 2005 reads the
Web.config file for the application many times when Visual Studio 2005 retrieves resource
information.WORKAROUNDTo work around this problem, use any of the following
methods. Method 1: Temporarily exclude the Web.config file- Use Visual Studio 2005 to open the project.
- In Solution
Explorer, right-click the Web.config file, and then click Exclude From
Project.
Note When you have to modify the Web.config file, right-click
the Web.config file in Solution Explorer, and then
click Include in Project.
Visual Studio 2005 performs more quickly if the Web.config file is
not read at all when you change between views. This method works best when the
ASP.NET server control does not require resource information at design time. Note You can also work around this problem by temporarily relocating
the .aspx file that you are using. Method 2: Adjust your workflowTry to adjust your workflow so that
you do not have to modify the ASP.NET server control after resource information
is generated. Because Design view performance is affected by the way that
Visual Studio 2005 retrieves resource information, you can save time by not using
resources until they are required. Method 3: Use Source viewTo work around this problem, use Source view to modify the code for
the ASP.NET server control. If you use Source view instead of Design view,
Visual Studio 2005 does not have to retrieve resource information when you change an
ASP.NET server control.
Modification Type: | Major | Last Reviewed: | 8/31/2006 |
---|
Keywords: | kbtshoot kbinfo kbprb KB916450 kbAudDeveloper |
---|
|