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 1948 on
Developer Community or GitHub 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
MD should not treat Mono.Posix as a framework assembly, ebacuse this breaks compatibility with compiling on .NET, were it certainly isn't a framework assembly.
For example, a Mono.Posix 126.96.36.199 reference in a 4.0 project on Windows will be handled literally, i.e. the assembly will have a reference to Mono.Posix 188.8.131.52 and Mono.Posix.dll will be local-copied into the bin folder.
On Mono, the reference will magically become a Mono.Posix 184.108.40.206 reference and the assembly will not be local-copied.
*** This bug has been marked as a duplicate of bug 1947 ***
Not a dup. One it about what MD itself references, the other is about how MD treats references.
We grab the assemblies from the Framework list. If we want it not to be a framework assembly, Mono itself should not list mono.posix in the framework directory.
We can special-case it, but there are multiple assemblies which fit this category.