[Nussu06]

fmtDouble and the Round branch in ImportProject::applyMSBuildStaticFunction cast the double result of a System.Math property function to long long without a range check, so a project value like $([System.Math]::Pow(10,30)) or $([System.Math]::Round(1e30)) is undefined behaviour (UBSan float-cast-overflow, as noted in the AI review on #8938). fmtDouble now takes the integer path only when the value fits in long long, and Round does its half-to-even step in double and formats through fmtDouble, so in-range results are unchanged and Round(1e30) gives the same text as Pow(10,30) instead of LLONG_MIN (out-of-range values still print via std::to_string rather than MSBuild's 1E+30, which is left for a separate change). Tested with new asserts in testMSBuildStaticFunctions, the full testrunner, and cppcheck --project on a crafted vcxproj with a UBSan build. I don't have Trac access, so could you create a ticket for this one?

[dmcppcheck]

There should probably be a trac ticket for this PR. Please create it, or ask us to create it. Then the PR title should be updated.