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
Developer Community or GitHub 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.
My Mono for Android solution builds fine on Windows using Visual Studio or MonoDevelop but won't build on the Mac using MonoDevelop. The error message I get when I try to build is "System.Security.Permissions.SecurityPermissions Attribute is obsolete. CAS support is not available with Silverlight applications (CS0618)."
On the Mac I'm using the following software:
- MonoDevelop 22.214.171.124
- Mono for Android 126.96.36.199234518.
On Windows I'm using the following software:
- Visual Studio 2010 10.0.40219.1 SP1Rel
- MonoDevelop 188.8.131.52
- Mono for Android 184.108.40.206234518
The code I'm trying to compile on the Mac is was originally ported from an Windows Mobile framework. I've searched the ported source code for the "System.Security.Permissions.SecurityPermissions" attribute but have not found anything. Google searches also don't turn up anything helpful.
Thanks in advance for your help. Let me know if you need additional information.
Trimble Navigation, Ltd.
It is hard to tell what is going on without the actual project. Could you attach your project (either publicly or marking it as private) so that we can investigate?
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?
If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.
Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.