[]c# double to string accuracy loss in pit-log

When the project encounters a large double value, then there are some unexpected conditions:

double b=1141.161994934082; b.tostring (); // ' 1141.16199493408 '

And then found that the last 2 was discarded, and finally tested this with a double number of digits related, if more than 16 bits, the last one will be discarded, that is, 2 is the 17th place, so was discarded, find a lot of ways have not solved the problem, so record.

When SQL Server 2014 is stored in this number, there is no problem, but from the query manager to see the number is also less a 2, that is, when the display is less than 2, the value of the time is a lot.

[]c# double to string accuracy loss in pit-log