Determines whether the runtime preserves legacy behavior in formatting operations with TimeSpan values.
The following sections describe attributes, child elements, and parent elements.
Specifies whether the runtime uses legacy formatting behavior with TimeSpan values.
The runtime does not restore legacy formatting behavior.
The runtime restores legacy formatting behavior.
The root element in every configuration file used by the common language runtime and .NET Framework applications.
Contains information about runtime initialization options.
Starting with the .NET Framework 4, the TimeSpan structure implements the IFormattable interface and supports formatting operations with standard and custom format strings. If a parsing method encounters an unsupported format specifier or format string, it throws a FormatException.
In previous versions of the .NET Framework, the TimeSpan structure did not implement IFormattable and did not support format strings. However, many developers mistakenly assumed that TimeSpan did support a set of format strings and used them in composite formatting operations with methods such as StringFormat. Ordinarily, if a type implements IFormattable and supports format strings, calls to formatting methods with unsupported format strings usually throw a FormatException. However, because TimeSpan did not implement IFormattable, the runtime ignored the format string and instead called the TimeSpanToString method. This means that, although the format strings had no effect on the formatting operation, their presence did not result in a FormatException.
For cases in which legacy code passes a composite formatting method and an invalid format string, and that code cannot be recompiled, you can use the <TimeSpan_LegacyFormatMode> element to restore the legacy TimeSpan behavior. When you set the enabled attribute of this element to true, the composite formatting method results in a call to TimeSpanToString rather than TimeSpanToString(String, IFormatProvider), and a FormatException is not thrown.
When you run the example on the .NET Framework 3.5 or on an earlier version, it displays the following output:
This differs markedly from the output if you run the example on the .NET Framework 4 or later version:
However, if you add the following configuration file to the example's directory and then run the example on the .NET Framework 4 or later version, the output is identical to that produced by the example when it is run on .NET Framework 3.5.
<?xml version ="1.0"?> <configuration> <runtime> <TimeSpan_LegacyFormatMode enabled="true"/> </runtime> </configuration>