FIX: You receive the NullReferenceException exception when you call the String.IsNullOrEmpty function in an application that is built on the .NET Framework 2.0
When you call the String.IsNullOrEmpty function in an application that is built on the Microsoft .NET Framework 2.0, you receive the NullReferenceException exception. This problem occurs if the following conditions are true:
You call the String.IsNullOrEmpty function by using a NULL parameter, and you use the function in a loop.
You build the application in release mode with the default build settings.
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only 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 2.0 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer 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.
The .NET Framework 2.0, x86-based versions
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Mscordacwks.dll
2.0.50727.915
802,304
02-Aug-2007
03:26
x86
Mscorjit.dll
2.0.50727.915
326,656
02-Aug-2007
03:26
x86
Mscorlib.dll
2.0.50727.915
4,308,992
02-Aug-2007
03:26
x86
Mscorpe.dll
2.0.50727.915
102,912
02-Aug-2007
03:26
x86
Mscorwks.dll
2.0.50727.915
5,634,560
02-Aug-2007
03:26
x86
Normalization.dll
2.0.50727.915
15,360
02-Aug-2007
03:26
x86
Normidna.nlp
Not Applicable
59,342
02-Aug-2007
03:26
Not Applicable
Normnfc.nlp
Not Applicable
45,794
02-Aug-2007
03:26
Not Applicable
Normnfd.nlp
Not Applicable
39,284
02-Aug-2007
03:26
Not Applicable
Normnfkc.nlp
Not Applicable
66,384
02-Aug-2007
03:26
Not Applicable
Normnfkd.nlp
Not Applicable
60,294
02-Aug-2007
03:26
Not Applicable
Peverify.dll
2.0.50727.915
136,192
02-Aug-2007
03:26
x86
Sos.dll
2.0.50727.915
382,464
02-Aug-2007
03:26
x86
Vsavb7rt.dll
8.0.50727.915
1,330,688
02-Aug-2007
03:26
x86
The .NET Framework 2.0, x64-based versions
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Mscordacwks.dll
2.0.50727.915
1,597,440
01-Aug-2007
19:14
x64
Mscordacwks.dll
2.0.50727.915
802,304
02-Aug-2007
03:26
x86
Mscorjit.dll
2.0.50727.915
1,588,736
01-Aug-2007
19:12
x64
Mscorjit.dll
2.0.50727.915
326,656
02-Aug-2007
03:26
x86
Mscorlib.dll
2.0.50727.915
3,960,832
01-Aug-2007
22:29
x64
Mscorlib.dll
2.0.50727.915
4,308,992
02-Aug-2007
03:26
x86
Mscorpe.dll
2.0.50727.915
157,184
01-Aug-2007
19:07
x64
Mscorpe.dll
2.0.50727.915
102,912
02-Aug-2007
03:26
x86
Mscorpjt.dll
2.0.50727.915
2,005,504
01-Aug-2007
19:13
x64
Mscorwks.dll
2.0.50727.915
10,327,040
01-Aug-2007
19:11
x64
Mscorwks.dll
2.0.50727.915
5,634,560
02-Aug-2007
03:26
x86
Normalization.dll
2.0.50727.915
18,432
01-Aug-2007
19:11
x64
Normalization.dll
2.0.50727.915
15,360
02-Aug-2007
03:26
x86
Normidna.nlp
Not Applicable
59,342
01-Aug-2007
19:14
Not Applicable
Normidna.nlp
Not Applicable
59,342
02-Aug-2007
03:26
Not Applicable
Normnfc.nlp
Not Applicable
45,794
01-Aug-2007
19:14
Not Applicable
Normnfc.nlp
Not Applicable
45,794
02-Aug-2007
03:26
Not Applicable
Normnfd.nlp
Not Applicable
39,284
01-Aug-2007
19:14
Not Applicable
Normnfd.nlp
Not Applicable
39,284
02-Aug-2007
03:26
Not Applicable
Normnfkc.nlp
Not Applicable
66,384
01-Aug-2007
19:14
Not Applicable
Normnfkc.nlp
Not Applicable
66,384
02-Aug-2007
03:26
Not Applicable
Normnfkd.nlp
Not Applicable
60,294
01-Aug-2007
19:14
Not Applicable
Normnfkd.nlp
Not Applicable
60,294
02-Aug-2007
03:26
Not Applicable
Peverify.dll
2.0.50727.915
205,824
01-Aug-2007
19:13
x64
Peverify.dll
2.0.50727.915
136,192
02-Aug-2007
03:26
x86
Sos.dll
2.0.50727.915
480,768
01-Aug-2007
19:21
x64
Sos.dll
2.0.50727.915
382,464
02-Aug-2007
03:26
x86
Vsavb7rt.dll
8.0.50727.915
1,330,688
02-Aug-2007
03:26
x86
The .NET Framework 2.0, Itanium architecture versions
To work around this problem, use one of the following methods:
In Visual studio 2005, right-click the project in Solution Explorer, click Properties on the Build tab, and then click to clear the Optimize code check box.
Replace all calls to the IsNullOrEmpty function inside a loop with the following:
Back to the top
