Why do I get a FormatException when converting a string to a float?

Question

When I try to convert a string to float:

Console.WriteLine(float.Parse("6.59"));

it throws an exception:

Unhandled Exception: System.FormatException: Input string was not in a correct f ormat.
at System.Number.ParseSingle(String value, NumberStyles options, NumberFormat Info numfmt)

When I try it like this:

Console.WriteLine(Convert.ToSingle("6.59"));

It throws the same exception:

Unhandled Exception: System.FormatException: Input string was not in a correct f ormat.
at System.Number.ParseSingle(String value, NumberStyles options, NumberFormat Info numfmt)
at System.Convert.ToSingle(String value)

Can you explain why this happens?

Have you tried breaking the code down into separate lines and stepping through on the debugger? — ChrisF
– ChrisF, Commented Apr 8, 2011 at 9:13

R. Martinho Fernandes · Accepted Answer · 2011-04-08 09:14:45Z

49

The single argument Parse method uses the current culture to parse the string. If your current culture uses some other decimal separator, this will fail.

Try using the invariant culture:

float.Parse("6.59", CultureInfo.InvariantCulture)

answered Apr 8, 2011 at 9:14

R. Martinho Fernandes

236k73 gold badges443 silver badges518 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Andre Lombaard Over a year ago

+1 for this useful tip, my code was working on my development environment but not in the production environment.

Jonas Van der Aa · Accepted Answer · 2011-04-08 09:26:04Z

5

The problem here is your culture.

Either set the invariant culture like this:

float.Parse("6.59", CultureInfo.InvariantCulture)

or use the correct decimal separator for your culture

float.Parse("6,59")

I wonder why you are using a literal string. If you are having problems entering literal floats, you can use

Console.WriteLine(6.59f)

If you do it this way culture doesn't matter because the value is decided at compile time.

edited Apr 8, 2011 at 9:26

answered Apr 8, 2011 at 9:19

Jonas Van der Aa

1,46112 silver badges27 bronze badges

2 Comments

R. Martinho Fernandes Over a year ago

The UK is Europe too! (I assumed the literal string was the result of trying to find "the simplest code that reproduces the problem").

Jonas Van der Aa Over a year ago

Blasted imperial units! Go Metric! (just kidding) I forgot that the UK still uses the imperial system :) But my point still stands, if he's going to put string literals into float.Parse he's doing it all wrong.

GvS · Accepted Answer · 2011-04-08 09:14:16Z

4

You are probably using a culture that uses the , as a decimal seperator.

You could try to Parse using the InvariantCulture:

float.Parse("6.59", CultureInfo.InvariantCulture)

answered Apr 8, 2011 at 9:14

GvS

52.5k16 gold badges104 silver badges139 bronze badges

Comments

Unknown · Accepted Answer · 2011-04-08 09:15:29Z

3

Culture - specific things. What's your default culture? Some cultures use "," instead of ".". You can try this:

float.Parse("6.59", CultureInfo.InvariantCulture);

answered Apr 8, 2011 at 9:15

Unknown

4112 silver badges5 bronze badges

Comments

Achinth Gurkhi · Accepted Answer · 2011-04-08 09:50:35Z

2

There could be problem with Locale/Culture. You need to set , instead of . for the decimal separator.

edited Apr 8, 2011 at 9:50

Achinth Gurkhi

2,1564 gold badges24 silver badges45 bronze badges

answered Apr 8, 2011 at 9:13

x2.

9,6586 gold badges43 silver badges63 bronze badges

1 Comment

R. Martinho Fernandes Over a year ago

Portuguese is even worse. Here . is the digit group separator (aka thousands separator). Because of this float.Parse("6.59") does not fail, but the result is 659. This has wasted me a couple of hours in the past :(

Sarel Esterhuizen · Accepted Answer · 2016-12-11 11:03:33Z

I know everyone here has already given the reason for the problem experienced but perhaps somebody should just expand on why Invariant fixes it.

The CultureInfo class is used either directly or indirectly by classes that format, parse, or manipulate culture-specific data, such as String, DateTime, DateTimeOffset, and the numeric types to deal with the differences in the way different cultures write these types.

In case of the decimal type some cultures use a period(.) whilst others use a comma (,). By default when you are using the Conversion Libraries it will make use of your local culture (that is the country your OS to configured for).

By specifying Invariant you say that you expect thousand separators to be commas(,) and decimal deliminator to be a period(.) as it is in most cultures.

A big problem that sometimes happens is that these cultural conventions change from the OS point of view. For example the South African (ZA) culture info used to behave like the invariant culture. Microsoft changed this with Windows 8 where the decimal suddenly became a comma and the thousand separator a space.This resulted in many legacy systems written in .Net suddently breaking when one migrated them to newer operating systems.

In the end, deal normalize all local culture info to invariant and persist and deal with them in your business logic in this format. Then localize it back on the front end. Same goes for DateTime, as soon as possible convert to UTC, and only back when you render an output.

user698555 · Accepted Answer · 2011-04-08 11:41:07Z

0

You could also try Convert class to perform this task.

Convert.ToDecimal("6.59");

answered Apr 8, 2011 at 11:41

user698555

1631 gold badge1 silver badge7 bronze badges

Collectives™ on Stack Overflow

Why do I get a FormatException when converting a string to a float?

7 Answers 7

1 Comment

2 Comments

Comments

Comments

1 Comment

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

7 Answers 7

1 Comment

2 Comments

Comments

Comments

1 Comment

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related