FIX: The Visual Studio .NET 2002 Macro IDE crashes after you apply certain ASP.NET fixes

Article ID: 816498 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

After you install certain Microsoft ASP.NET hotfixes, Microsoft Visual Studio .NET 2002 crashes when you try to access the Macro IDE. For a list of these hotfixes, see the "More information" section of this article.
Back to the top | Give Feedback

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 .NET Framework 1.0 Service Pack 3 or .NET Framework 1.1 Service Pack 1 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:
http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
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.

The English version of this hotfix has the file attributes (or later) 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 tool in Control Panel. 
  Date         Time   Version     Size     File Name
  -----------------------------------------------------
  06-Mar-2003  09:32  7.0.9674.0  352,256  Vsmacros.dll
Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
Back to the top | Give Feedback

MORE INFORMATION

Steps to reproduce the problem

  1. Apply one of the following ASP.NET hotfixes:
    326366
    (http://support.microsoft.com/kb/326366/ )
    Fatal Execution Engine error when AppDomain unloads
    327135
    (http://support.microsoft.com/kb/327135/ )
    BeforeNavigate2 event of WebBrowser control does not fire
    327256
    (http://support.microsoft.com/kb/327256/ )
    FIX: Memory leak of permission objects in a managed heap
    327132
    (http://support.microsoft.com/kb/327132/ )
    FIX: PassportIdentity does not require secure PIN when security-enhanced authentication is requested
    327523
    (http://support.microsoft.com/kb/327523/ )
    Users can open Web pages without the correct NTFS permissions
    327418
    (http://support.microsoft.com/kb/327418/ )
    FIX: "Leaving Secure Connection" message when you use LinkButton in DataGrid and SSL
    327795
    (http://support.microsoft.com/kb/327795/ )
    FIX: Repeatedly retrieving remote performance counters may fail with status 1450
    328369
    (http://support.microsoft.com/kb/328369/ )
    FIX: PerformanceCounter class keeps remote registry handle open
    318320
    (http://support.microsoft.com/kb/318320/ )
    Error message when you submit .aspx page with SmartNav under SSL
    328267
    (http://support.microsoft.com/kb/328267/ )
    FIX: Aspnet_wp.exe is recycled because of a false deadlock
    325699
    (http://support.microsoft.com/kb/325699/ )
    COM Interop cannot properly deal with a disconnected stub
    328534
    (http://support.microsoft.com/kb/328534/ )
    FIX: "The XML File \\MyComputer\MyShare\Web.config Could Not Be Loaded" error message
    329250
    (http://support.microsoft.com/kb/329250/ )
    FIX: Stronger credentials for processModel, identity, and sessionState
    329956
    (http://support.microsoft.com/kb/329956/ )
    FIX: Requests are not removed from ASP.NET request table
    329519
    (http://support.microsoft.com/kb/329519/ )
    FIX: Memory leak in semaphores and events
    329959
    (http://support.microsoft.com/kb/329959/ )
    FIX: Requests Current and Requests in Application Queue performance monitor counters added in ASP.NET
    330469
    (http://support.microsoft.com/kb/330469/ )
    FIX: ASP.NET health monitoring does not work on servers that are running many processes
    330900
    (http://support.microsoft.com/kb/330900/ )
    FIX: ExecutionEngineException error after a typical exception is thrown
    813078
    (http://support.microsoft.com/kb/813078/ )
    FIX: Postbacks may fail when SmartNav is on
    812399
    (http://support.microsoft.com/kb/812399/ )
    FIX: "The View State Is Invalid for This Page and Might Be Corrupted" when the View State contains objects that have long decimals
    810281
    (http://support.microsoft.com/kb/810281/ )
    Error Message: Cannot access file AssemblyName because it is being used by another process
    810328
    (http://support.microsoft.com/kb/810328/ )
    FIX: Hotfix 324735 causes ASPX pages to generate HTML that does not postback correctly on Pocket PC 2002
    810178
    (http://support.microsoft.com/kb/810178/ )
    FIX: Memory leak when throwing exceptions from nested exception blocks
    810245
    (http://support.microsoft.com/kb/810245/ )
    FIX: Invalid object in ASP session state
    812686
    (http://support.microsoft.com/kb/812686/ )
    FIX: When you call the Response.ClearHeaders method in a custom HTTPmodule, extra characters are appended to the output
    812280
    (http://support.microsoft.com/kb/812280/ )
    FIX: EventLogEntry class may cause leaks in Thread Local Storage and Event ID 4199 event log entries
    813413
    (http://support.microsoft.com/kb/813413/ )
    FIX: Compiler error when ASP.NET tries to start the CSC compiler
    813105
    (http://support.microsoft.com/kb/813105/ )
    FIX: .NET Framework implementation of IEnumConnections::Next causes the client application to stop responding
    810280
    (http://support.microsoft.com/kb/810280/ )
    FIX: After an AppDomain unload, the ASP.NET worker process uses 100 percent of the CPU
    812832
    (http://support.microsoft.com/kb/812832/ )
    ASP.NET configuration file processing ignores the codebase hints that appear in the Machine.config file
    813350
    (http://support.microsoft.com/kb/813350/ )
    FIX: "Category Not Found" error message when you run a new Visual Studio .NET application in a side-by-side environment
    812693
    (http://support.microsoft.com/kb/812693/ )
    FIX: Unexpected results for .NET-connected assemblies that were compiled by using the JIT Compiler and that contain some operators
    814687
    (http://support.microsoft.com/kb/814687/ )
    FIX: An orphaned critical section may cause the ASP.NET worker process to stop responding
    814206
    (http://support.microsoft.com/kb/814206/ )
    FIX: Calling Server.Transfer skips execution of custom HTTP filters
    811672
    (http://support.microsoft.com/kb/811672/ )
    FIX: You receive an "Unhandled Exception" error message when you run an application that uses valid C code
    813340
    (http://support.microsoft.com/kb/813340/ )
    FIX: You receive a "System.NullReferenceException: object reference not set to an instance of an object" error message when you implement JIT optimization by using a float
    328546
    (http://support.microsoft.com/kb/328546/ )
    INFO: Post-Service Pack 2 .NET Framework ASP.NET hotfix package
  2. Open the Visual Studio .NET IDE.
  3. Open the Macro IDE window by pressing ALT+F11. Notice that Visual Studio .NET crashes
Back to the top | Give Feedback

Properties

Article ID: 816498 - Last Review: October 10, 2005 - Revision: 3.6
APPLIES TO
  • Microsoft .NET Framework 1.1
  • Microsoft .NET Framework 1.0
Keywords: 
kbhotfixserver kbqfe kbbug kbfix KB816498
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top