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 34781 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
When calling a method/property that displays a yellow underline in source code with the message "Warning: Mono TODO", customer asks fi there is a way to force a build error when using this code. An example is the static "HttpWebRequest.DefaultMaximumErrorResponseLength" property. This does show the warning in the source code, but the build succeeds and instead, understandably, throws a NotImplemented exception at run time.
## Steps to reproduce.
1. Open Xamarin studio and create a new Xamarin.Mac project.
2. Add the following line of code in the ViewController's ViewDidLoad override:
var errorlength = HttpWebRequest.DefaultMaximumErrorResponseLength;
The expected result is as actual, but the question is whether the above can cause a build error rather than only a source code warning and a run time exception.
This was be a non-trivial amount of work. We could have our linker scan their entire program, come up with a list of all BCL methods called, and then reflect for the TODO attribute.
is a tool we already have that does this.
I'm going to keep this around in case other
^ thanks bugzilla.
in case other people request this feature, but right now it is a low priority, since we already have a released tool you can integrate into your build process if you desire.