Introduction

Microsoft has released a cumulative update for Microsoft Visual Studio 2008 and for Microsoft Visual Web Developer Express 2008.

Back to the top

Bugs that are fixed in this cumulative update for Visual Studio 2008 and for Visual Web Developer Express 2008 include the following.

Back to the top

Bugs in HTML Source View performance

•	In Visual Studio 2008, you have a page that contains an ActiveX control. The ActiveX control has more than two levels of subproperties. When you type inside the page, the source editor stops responding for several seconds.
•	The View Code command in Visual Studio 2008 is not available for a long time.
•	When you open large HTML documents in Visual Studio 2008, performance is slow.
•	When you work with large HTML files by using Visual Studio 2008, Visual Studio does not respond.
•	When you press TAB or SHIFT+TAB to indent or to un-indent a large amount of code that you have selected in Visual Studio 2008, performance is slow.

Back to the top

Bug in Design view performance

•	When Design view is configured by using certain page markup in Visual Studio 2008, performance is slow when you type inside Design view.

Back to the top

Bugs in HTML editing

•	Quotation marks (") are not inserted after the Class attribute or after the CssClass attribute even though the Insert attribute value quotes when typing option is enabled.
•	When the ServiceReference element points to the current Web page, Visual Studio 2008 crashes.

Back to the top

Bugs in JavaScript editing

•	When you open a JavaScript file, the colorization of the client script is delayed several seconds.
•	When IntelliSense encounters a property that has an empty string, JavaScript IntelliSense does not work.

Back to the top

Bugs in Web site building performance

•	The Bin folder of a project contains many assemblies and .refresh files. When you build the project in Visual Studio 2008, performance is slow.

Back to the top

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:Note The MSDN Code Gallery displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

For more information about the MSDN Code Gallery, visit the following Microsoft Web site:

Prerequisites

You must have Visual Studio 2008 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

File name	File version	File size	Date	Time	Platform
Htmled.dll	9.0.21022.46	2419192	01-Feb-2008	17:35	x86
Microsoft.visualstudio.web.dll	9.0.21022.46	1024000	01-Feb-2008	17:35	x86
Mswebprj.dll	9.0.21022.46	1410560	01-Feb-2008	17:35	x86
Typelibbuilder.exe	9.0.21022.46	304136	01-Feb-2008	17:35	x86

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Back to the top

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top