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 1947 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
Mono.Posix on Mono is a pseudo-framework assembly. If you build on Mono 4.0 runtime referencing any version of Mono.Posix, you get a 126.96.36.199 reference. However, on Windows, MD's built against Mono.Posix 188.8.131.52 (which works fine on 4.0 framework).
The problem is if an addin is built on Mono and distributed to Windows via the addin server, the addin will reference Mono.Posix 184.108.40.206, but this will fail to work on Windows because MD on Windows only has 220.127.116.11.
*** Bug 1948 has been marked as a duplicate of this bug. ***
Is there some workaround of that bug?
I'm writing monodevelop addin right now and got that problem.
I've updated Xamarin to the latest stable for VS2015. No matter what I do I keep getting this error. I haven't had this problem before. I think it is something to do with the latest Xamarin.
@Suat - This particular bug is to do with MonoDevelop not Visual Studio on Windows. I suspect you are hitting this VS on Windows bug #56787