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 for Bug 38515 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
this.ProductionVersion of a System.Windows.Forms application is supposed to get the info from AssemblyVersion Attribute.
But it does not. I don't know where it is getting the info from, but it is wrong. The same binary work correctly under wine + .net2.
A macintosh user (running a mono mkbundled binary) reports that "Help", "About Font Validator" shows 1.0 instead of 1.1.
I looked at the code a bit, and anyway, "mono FontVal.exe" on native Linux shows 1.0, but the same binary under wine + dotnet framework 2 installed with winetricks (instead of wine-mono) shows 1.1 . So native mono on linux is not behaving correctly compared to dotnet framework 2 under wine.
Here is the binary bundle. Just unzip and run FontVal.exe under mono vs dotnet, and look at 'Help', 'about...'
Sorry, please ignore the posted binary url and much of the info. I was already starting to play with AssemblyInformationalVersion , which indeed behaves differently under mono vs under dotnet, so there is indeed a bug, just not where I said it was.
I have another binary built with Microsoft visual c#. Comparing with it, I think I found another bug. There seems to be two bugs relating to this, one to do with the mono compiler and the other to do with the mono runtime:
- the mono compiler does not copy AssemblyVersion into System.Diagnostics.FileVersionInfo, the Microsoft compiler does.
- the mono runtime does not copy System.Diagnostics.FileVersionInfo
into System.Windows.Forms Application.ProductVersion, the Microsoft dot net runtime does.