Question

Update

I’ve found the problem, the exception came from a 2nd field on the same form which indeed should have prompted it (because it was empty)… I was looking at an error which I thought came from trying to parse one string, when in fact it was from trying to parse another string… Sorry for wasting your time.

Original Question

I’m completely dumbfounded by this problem. I am basically running int.Parse("32") and it throws a FormatException. Here’s the code in question:

private double BindGeo(string value)
{
    Regex r = new Regex(@"\D*(?<deg>\d+)\D*(?<min>\d+)\D*(?<sec>\d+(\.\d*))");
    Regex d = new Regex(@"(?<dir>[NSEW])");
    var numbers = r.Match(value);
    string degStr = numbers.Groups["deg"].ToString();
    string minStr = numbers.Groups["min"].ToString();
    string secStr = numbers.Groups["sec"].ToString();
    Debug.Assert(degStr == "32");
    var deg = int.Parse(degStr);
    var min = int.Parse(minStr);
    var sec = double.Parse(secStr);
    var direction = d.Match(value).Groups["dir"].ToString();
    var result = deg + (min / 60.0) + (sec / 3600.0);
    if (direction == "S" || direction == "W") result = -result;
    return result;
}

My input string is "32 19 17.25 N"

The above code runs on a .NET 4 web hosting service (aspspider) on an ASP.NET MVC 3 web application (with Razor as its view engine).

Note the assersion of degStr == "32" is valid! Also when I take the above code and run it in a console application it works just fine. I’ve scoured the web for an answer, nothing…

Any ideas?

UPDATE (stack trace)

[FormatException: Input string was not in a correct format.]
   System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) +9586043
   System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) +119
   System.Int32.Parse(String s) +23
   ParkIt.GeoModelBinder.BindGeo(String value) in C:\MyProjects\ParkIt\ParkIt\GeoBinder.cs:42

Line 42 is var deg = int.Parse(degStr); and note that the exception is in System.Int32.Parse (not in System.Double as was suggested).

Answer 1

It turns out that this is a non-question. The problem was that the exception came from a 2nd field on the same form which indeed should have prompted it (because it was empty)… I was looking at an error which I thought came from trying to parse one string, when in fact it was from trying to parse another string…

Sorry for wasting your time.