.net fw vs .net core calculations

S-Soft 646 Reputation points
2022-11-04T22:56:23.693+00:00

hello
any idea what's going on here?
257350-index.jpg

Visual Studio
Visual Studio
A family of Microsoft suites of integrated development tools for building applications for Windows, the web and mobile devices.
4,784 questions
C#
C#
An object-oriented and type-safe programming language that has its roots in the C family of languages and includes support for component-oriented programming.
10,519 questions
VB
VB
An object-oriented programming language developed by Microsoft that is implemented on the .NET Framework. Previously known as Visual Basic .NET.
2,636 questions
0 comments No comments
{count} votes

Accepted answer
  1. P a u l 10,411 Reputation points
    2022-11-05T00:57:20.16+00:00

    This was due to a change in the parsing/formatting of single/double precision floating point numbers as of .NET 3.

    The change makes floating point numbers more IEEE compliant with the aim to make numbers "round-trippable" (i.e. double.Parse(value.ToString()) == value )

    There's more information in this blog with some links to the GH issues that spawned the conversation if you're interested in a drilldown any further:
    https://devblogs.microsoft.com/dotnet/floating-point-parsing-and-formatting-improvements-in-net-core-3-0/

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful