120

What is the difference between Parse() and TryParse()?

int number = int.Parse(textBoxNumber.Text);

// The Try-Parse Method
int.TryParse(textBoxNumber.Text, out number);

Is there some form of error-checking like a Try-Catch Block?

Matt Davis
  • 45,297
  • 16
  • 93
  • 124
Kredns
  • 36,461
  • 52
  • 152
  • 203

8 Answers8

173

Parse throws an exception if it cannot parse the value, whereas TryParse returns a bool indicating whether it succeeded.

TryParse does not just try/catch internally - the whole point of it is that it is implemented without exceptions so that it is fast. In fact the way it is most likely implemented is that internally the Parse method will call TryParse and then throw an exception if it returns false.

In a nutshell, use Parse if you are sure the value will be valid; otherwise use TryParse.

Greg Beech
  • 133,383
  • 43
  • 204
  • 250
  • 2
    "internally the Parse method will call TryParse" Except that Parse pre-dates TryParse by several versions. Of course, they could have moved the core implementation to TryParse... – Joel Coehoorn Jan 22 '09 at 01:10
  • 4
    @Joel - I assumed they would have moved the implementation, but I just had a look with reflector and they are separate implementations with *exactly* the same code other than one has 'throw ...' and one has 'return false'. I wonder why they aren't consolidated?! – Greg Beech Jan 22 '09 at 08:39
  • 7
    Although, thinking about it, Parse throws a number of different exceptions so if all it had was a bool from TryParse then it wouldn't know which one to throw. – Greg Beech Jan 22 '09 at 08:42
  • 6
    "use Parse if you are sure the value will be valid". I'd add, "but you acknowledge the possibility you might be wrong". If you were 100% sure it can parse, then you could just as correctly use TryParse which might be faster. – Jon Feb 15 '13 at 12:42
  • 2
    And by "different exceptions", @GregBeech means the message, not the class. – Paul Draper Apr 19 '13 at 20:05
32

If the string can not be converted to an integer, then

  • int.Parse() will throw an exception
  • int.TryParse() will return false (but not throw an exception)
Gilad Green
  • 36,708
  • 7
  • 61
  • 95
M4N
  • 94,805
  • 45
  • 217
  • 260
  • What if I use int.TryParse(some_method_that_throws_exception(), out int test)? Will it catch any exception or only the ones related to parsing? – Alexandru Antochi Nov 12 '18 at 17:19
  • 2
    @AlexandruAntochi You should not ask a question as a comment. This will make it almost impossible for others to benefit from useful answers. However, to make it worth your while, the answer to your question is no, int.TryParse will not throw at all. If the method fail to parse, it will only reflect this by a return value of false. This makes it convenient to use if(int.TryParse… to only do something if the parse succeeds. – Rob Jan 23 '19 at 17:00
4

The TryParse method allows you to test whether something is parseable. If you try Parse as in the first instance with an invalid int, you'll get an exception while in the TryParse, it returns a boolean letting you know whether the parse succeeded or not.

As a footnote, passing in null to most TryParse methods will throw an exception.

Ray Booysen
  • 28,894
  • 13
  • 84
  • 111
4

TryParse and the Exception Tax

Parse throws an exception if the conversion from a string to the specified datatype fails, whereas TryParse explicitly avoids throwing an exception.

Gulzar Nazim
  • 51,744
  • 26
  • 128
  • 170
0

I know its a very old post but thought of sharing few more details on Parse vs TryParse.

I had a scenario where DateTime needs to be converted to String and if datevalue null or string.empty we were facing an exception. In order to overcome this, we have replaced Parse with TryParse and will get default date.

Old Code:

dTest[i].StartDate = DateTime.Parse(StartDate).ToString("MM/dd/yyyy");
dTest[i].EndDate = DateTime.Parse(EndDate).ToString("MM/dd/yyyy");

New Code:

DateTime startDate = default(DateTime);
DateTime endDate=default(DateTime);
DateTime.TryParse(dPolicyPaidHistories[i].StartDate, out startDate);
DateTime.TryParse(dPolicyPaidHistories[i].EndDate, out endDate);

Have to declare another variable and used as Out for TryParse.

LifeOfPi
  • 625
  • 5
  • 19
  • You don't need to initialize `startDate` and `endDate` as [`DateTime.TryParse`](https://msdn.microsoft.com/en-us/library/ch92fbc1(v=vs.110).aspx) will always overwrite them with `DateTime.MinValue`. If incorrect date representations should be converted to a different value, check the return value of `DateTime.TryParse` and if it is false, set the value explicitly. – Palec May 31 '17 at 09:43
  • Using `DateTime?` (**DateTime nullable**) – Kiquenet Jun 10 '17 at 17:55
0

TryParse does not return the value, it returns a status code to indicate whether the parse succeeded (and doesn't throw an exception).

Mark Brittingham
  • 28,545
  • 12
  • 80
  • 110
0

For the record, I am testing two codes: That simply try to convert from a string to a number and if it fail then assign number to zero.

        if (!Int32.TryParse(txt,out tmpint)) {
            tmpint = 0;
        }

and:

        try {
            tmpint = Convert.ToInt32(txt);
        } catch (Exception) {
            tmpint = 0;
        }

For c#, the best option is to use tryparse because try&Catch alternative thrown the exception

A first chance exception of type 'System.FormatException' occurred in mscorlib.dll

That it is painful slow and undesirable, however, the code does not stop unless Debug's exception are settled for stop with it.

magallanes
  • 6,583
  • 4
  • 54
  • 55
  • The first code snippit doesn't do anything, since tmpint will already be set to zero if the string is not able to be parsed as an int. – Andrew Neely Jun 29 '15 at 15:06
-1

double.Parse("-"); raises an exception, while double.TryParse("-", out parsed); parses to 0 so I guess TryParse does more complex conversions.

o17t H1H' S'k
  • 2,541
  • 5
  • 31
  • 52