Base types, Collections, Diagnostics, IO, RegEx…
The BCL Team has here published new official guidance for using Strings in .NET 2.0. It is highly recommended that .NET developers use these new best practices and new Framework types when developing on the second major version of the Framework.
The full paper can be found here: http://msdn.microsoft.com/netframework/default.aspx?pull=/library/en-us/dndotnet/html/StringsinNET20.asp
The following is a snippet of the paper:
The Microsoft .NET Framework enables developers to create software fully ready for localization and internationalization, through comprehensive machinery under the hood designed for, among other tasks, correctly interpreting strings given the current locale. This aids in quickly creating and using solutions designed for a broad range of cultures. But, when culturally-irrelevant string data is interpreted by these methods, code can exhibit subtle bugs and operate slower than necessary on untested cultures.
When interpreting strings, the canonical example of a culturally-aware type, sometimes flipping the culture switch causes unexpected results. The same strings can sort, case, and compare differently under different Thread.CurrentCulture settings. Sometimes strings should be allowed to vary according to the user's culture (for display data), but for most strings internal to an application, such as XML tags, user names, file paths, and system objects, the interpretation should be consistent throughout all cultures. Additionally, when strings represent such symbolic information, comparison operations should be interpreted entirely non-linguistically.
Recommendations for String Use
When developing with the 2.0 version of the .NET Framework, keeping a few very simple recommendations in mind will suffice to solve confusion about using strings.
Many new and recommended String method overloads consume a StringComparison parameter, making these choices explicit:
String protocol = MyGetUrlProtocol();
if (String.Compare(protocol, "ftp", StringComparsion.Ordinal) != 0)
throw new InvalidOperationException();
String filename = args;
if (String.EndsWith(filename, "txt", StringComparison.OrdinalIgnoreCase))
reader = File.OpenText(filename);
Hi, You may find this problem being arised by your customers. You can find the description in the KB:
The Visual Studio 2010 and .NET Framework 4.0 CTP is available for download as of last week. The CTP
PingBack from http://www.hilpers.com/1040872-q-new-recommendations-for-using
A BCL csapat közzétette azokat az új képességeket, amiket a várhatóan ez év második felében megjelenő
PingBack from http://woodtvstand.info/story.php?id=5723