When you port a Microsoft Visual C# .NET 2003 project to Microsoft Visual C# 2005, the project may take significantly longer to compile. For example, a project that you compile in several seconds in Visual C# .NET 2003 may take several minutes to compile in Visual C# 2005.
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 Microsoft .NET Framework 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 the .NET Framework 2.0 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.
Collapse this tableExpand this table
| File name | File version | File size | Date | Time |
|---|
| Mscordacwks.dll | 2.0.50727.166 | 801,280 | 13-Jun-2006 | 07:03 |
| Mscorlib.dll | 2.0.50727.166 | 4,317,184 | 13-Jun-2006 | 07:03 |
| Normalization.dll | 2.0.50727.166 | 15,360 | 13-Jun-2006 | 07:03 |
| Normidna.nlp | 2.0.50727.166 | 59,342 | 13-Jun-2006 | 07:03 |
| Normnfc.nlp | 2.0.50727.166 | 45,794 | 13-Jun-2006 | 07:03 |
| Normnfd.nlp | 2.0.50727.166 | 39,284 | 13-Jun-2006 | 07:03 |
| Normnfkc.nlp | 2.0.50727.166 | 66,384 | 13-Jun-2006 | 07:03 |
| Normnfkd.nlp | 2.0.50727.166 | 60,294 | 13-Jun-2006 | 07:03 |
| SOS.dll | 2.0.50727.166 | 377,344 | 13-Jun-2006 | 07:03 |
| Mscorwks.dll | 2.0.50727.166 | 5,623,808 | 13-Jun-2006 | 07:03 |
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684Â
(http://kbalertz.com/Feedback.aspx?kbNumber=824684/
)
Description of the standard terminology that is used to describe Microsoft software updates