Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 2307350 - Last Review: August 5, 2010 - Revision: 9.0
Servicing a Microsoft .NET Framework component will trigger a repair of the entire .NET feature set
When you install a hotfix that updates any Microsoft .NET Framework component on a computer running Microsoft Windows 2003 or earlier, the patched component will trigger a repair of the entire .NET feature set. When the feature set is repaired, it will repair all sub-features and their dependencies as well. Since Microsoft ASP.NET is part of the .NET Framework feature set, a feature set repair for the updated .NET framework component will trigger all of the custom actions associated with an ASP.NET feature repair as well. Even if the .NET hotfix does not directly update an ASP.NET component, it will still trigger a repair of the ASP.NET feature set.Â
During an ASP.NET feature set repair routine, the servicing simply calls aspnet_regiis.exe with "-iru" parameters. This routine performs a number of checks and takes certain actions that could possibly change the ASP.NET configuration under very rare circumstances. As mentioned above, this routine will run even if no ASP.NET components are getting updated by the hotfix, and therefore also has the potential to alter some ASP.NET configuration settings. Installation of such a hotfix will also trigger IIS and ASP.NET application domain restarts.Â
Microsoft recommends that you backup your IIS and ASP.NET configuration files before installing any hotfix that updates Microsoft .NET Framework components.Â
Prior to Microsoft .NET Framework 4.0, the ASP.NET feature set was always installed as part of .NET Framework feature set. Starting with Microsoft .NET Framework 4.0, ASP.NET does not take feature set dependencies from the .NET framework, and therefore the issue described in this article does not apply to Microsoft .NET Framework 4.0 servicing.Â
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See
Terms of Use
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations.
APPLIES TO
- Microsoft .NET Framework 1.0
- Microsoft .NET Framework 1.0 Service Pack 3
- Microsoft .NET Framework 1.1
- Microsoft .NET Framework 1.1 Service Pack 1
- Microsoft .NET Framework 2.0
- Microsoft .NET Framework 2.0 IA64 Edition
- Microsoft .NET Framework 2.0 Service Pack 1 (x86)
- Microsoft .NET Framework 2.0 Service Pack 2
- Microsoft .NET Framework 2.0 x64 Edition
- Microsoft .NET Framework 3.0
- Microsoft .NET Framework 3.0 Service Pack 1
- Microsoft .NET Framework 3.0 Service Pack 2
- Microsoft .NET Framework 3.5
- Microsoft .NET Framework 3.5 Service Pack 1
- Microsoft ASP.NET 1.1
- Microsoft ASP.NET 1.0
- Microsoft ASP.NET 2.0
- Microsoft ASP.NET 3.5
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate