Quote:
I tried bool.Parse and bool.TryParse but in both situations the same exception is throws.
No, you didn't. TryParse specifically never throws an exception - it always returns a true / false indicator to show if the value was converted or not. If your modified code throws an exception with TryParse, then it's not the line you think it is that causes the problem.
The trouble is, this problem involves your data as well as your code, and we have no access to that. So, it's going to be up to you.
Fortunately, you have a tool available to you which will help you find out what is going on: the debugger. If you don't know how to use it then a quick Google for "Visual Studio debugger" should give you the info you need.
Put a breakpoint on the first line in the function, and run your code through the debugger. Then look at your code, and at your data and work out what should happen manually. Then single step each line checking that what you expected to happen is exactly what did. When it isn't, that's when you have a problem, and you can back-track (or run it again and look more closely) to find out why.
Sorry, but we can't do that for you - time for you to learn a new (and very, very useful) skill: debugging!