Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
GitHub or Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
A decimal zero with multiple digits of precision (e.g "0.0m", "0.00m") should convert to string with the same precision as originally specified (according to csc), but mcs always returns "0". This behavior occurs both with decimal.Parse("0.0").ToString() as well as the literal 0.0m.ToString().
Non-zero values with multiple zero digits of precision (e.g. "1.000") appear to work properly.
// Expected Output (csc):
// Actual Output (mcs):
Fixed in master
Hi Marek. I see this fixed in the github repository main branch:
I apologize for my ignorance on the mono pipeline. But when can I expect to see this version in an official release?
I'm using Xamarin Studio with Mono 2.10.12, and the git branch for mono-2-10 doesn't have the fix, and the code still outputs "0" for "decimal.Parse("0.00").ToString().
Here are my details from Xamarin Studio About:
Version 4.0.3 (build 13)
Installation UUID: c26858de-4307-46b9-9b68-5d27be3d7784
Mono 2.10.12 (mono-2-10/c9b270d)
Package version: 210120000
Thanks for the fix! I'd just like to use it in my code! (Note: I'm setting this to REOPENED because I'm not sure if you'll get notification if I only add a comment).
You need to download Mono 3.0