TryParse更快…

The first of these functions, Parse, is one that should be familiar to any .Net developer. This function will take a string and attempt to extract an integer out of it and then return the integer. If it runs into something that it can’t parse then it throws a FormatException or if the number is too large an OverflowException. Also, it can throw an ArgumentException if you pass it a null value. TryParse is a new addition to the new .Net 2.0 framework that addresses some issues with the original Parse function. The main difference is that exception handling is very slow, so if TryParse is unable to parse the string it does not throw an exception like Parse does. Instead, it returns a Boolean indicating if it was able to successfully parse a number. So you have to pass into TryParse both the string to be parsed and an Int32 out parameter to fill in. We will use the profiler to examine the speed difference between TryParse and Parse in both cases where the string can be correctly parsed and in cases where the string cannot be correctly parsed. The Convert class contains a series of functions to convert one base class into another. I believe that Convert.ToInt32(string) just checks for a null string (if the string is null it returns zero unlike the Parse) then just calls Int32.Parse(string). I’ll use the profiler to confirm this and to see if using Convert as opposed to Parse has any real effect on performance.

带有示例的源代码

希望这能有所帮助。

区别在于:

Int32.Parse()和Int32.TryParse()只能转换字符串。Convert.ToInt32()可以接受任何实现IConvertible的类。如果传递给它一个字符串，那么它们是等效的，除了类型比较等额外开销。如果要转换字符串，那么TryParse()可能是更好的选择。

没有区别。 Convert.ToInt32()在内部调用int.Parse()

除了一件事Convert.ToInt32()当参数为空时返回0

否则两者的工作方式是一样的

这是int的一个细节。解析和转换。ToInt32: 比如说，你有一个char数组，char[] a=['1'，'2'，'3'，'4']，你想把每个元素转换成一个整数。 Convert.ToInt32([0])会给你一个数字49。它将其视为ASCII码 int.Parse(a[0])将为您提供正确的输出，即1

如果你有一个字符串数组string[] b=['1'，'2'，'3'，'4']，那么转换。ToInt32和int。Parse在输出上没有区别。两者都返回正确的整数。

TryParse更快…

The first of these functions, Parse, is one that should be familiar to any .Net developer. This function will take a string and attempt to extract an integer out of it and then return the integer. If it runs into something that it can’t parse then it throws a FormatException or if the number is too large an OverflowException. Also, it can throw an ArgumentException if you pass it a null value. TryParse is a new addition to the new .Net 2.0 framework that addresses some issues with the original Parse function. The main difference is that exception handling is very slow, so if TryParse is unable to parse the string it does not throw an exception like Parse does. Instead, it returns a Boolean indicating if it was able to successfully parse a number. So you have to pass into TryParse both the string to be parsed and an Int32 out parameter to fill in. We will use the profiler to examine the speed difference between TryParse and Parse in both cases where the string can be correctly parsed and in cases where the string cannot be correctly parsed. The Convert class contains a series of functions to convert one base class into another. I believe that Convert.ToInt32(string) just checks for a null string (if the string is null it returns zero unlike the Parse) then just calls Int32.Parse(string). I’ll use the profiler to confirm this and to see if using Convert as opposed to Parse has any real effect on performance.

带有示例的源代码

希望这能有所帮助。

这取决于参数类型。例如，我今天刚刚发现，它将使用ASCII值直接将char转换为int。这不是我想要的功能…

我警告过你!

public static int ToInt32(char value)
{
    return (int)value;
} 

Convert.ToInt32('1'); // Returns 49
int.Parse('1'); // Returns 1