FIX: The Visual Studio IDE crashes when you compile a large Visual Basic solution (909085)

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Visual Basic .NET 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have Microsoft Visual Basic .NET 2003 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.

Visual Studio .NET 2003 32-bit Hotfix

File name	File version	File size	Date	Time	Platform
bcaut.dll	7.10.5021.0	598,016	06-Oct-2005	05:04	Not Applicable
msvb7.dll	7.10.5021.0	1,441,792	06-Oct-2005	11:12	Not Applicable

0:000> kL
ChildEBP RetAddr  
0012f500 52ab383e kernel32!RaiseException+0x51
0012f548 52a37975 msvb7!PEBuilder::CompileToDisk+0xb2
0012f7c4 52a378e2 msvb7!CompilerProject::FinishCompile+0x3b
0012f7d0 52a379a7 msvb7!CompilerPackage::EndProjectCompilation+0x5d
0012f7e0 77d0612f msvb7!Messages::WndProc+0x65
0012f80c 77d069a5 user32!InternalCallWinProc+0x1b
0012f884 77d06689 user32!UserCallWinProcCheckWow+0x151
0012f8ec 77d0faec user32!DispatchMessageWorker+0x327
0012f8f8 500126c6 user32!DispatchMessageA+0xb
0012f92c 50012714 msenv!CSUIBuilder::PumpMessages+0x63
0012f934 5677bc2a msenv!CSUIBuilder::Tick+0xa
0012f968 5677bbd5 msvbprj!CVsProjBuildableProjectCfg::AdviseTick+0x30
0012f97c 5677bb7a msvbprj!CVsProjBuildableProjectCfg::TickEx+0x68
0012f99c 5677bb44 msvbprj!CVbBldCompiler::TickEx+0x32
0012f9b0 52a37831 msvbprj!CVbBldCompilerEvents::TickEx+0x26
0012f9cc 52a3784c msvb7!CompilerPackage::TickCompile+0x3b
0012f9d8 77d0612f msvb7!Messages::WndProc+0x50
0012fa04 77d069a5 user32!InternalCallWinProc+0x1b
0012fa7c 77d06689 user32!UserCallWinProcCheckWow+0x151