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.
Toggling the public/private setting in the assembly browser doesn't take effect immediately, only after closing and reopening it.
The assembler browser should use options (they're now global, not per-node) instead of implementing its own.
Works for me:
Why should it use these options ? Where is the benefit ?
Hm, now I can't reproduce, same build. But it definitely happened multiple times, so I've leaving it open.
The reason I suggested using the options is that there's less code and a single implementation to debug.
I'm not really happy with the speed of the tree - therefore I don't want to dig deeper into the extensible tree view code again.
When I'm in the mood & have some time I want to make an own control for showing the tree.
If the 'Refresh' method from the treeview works - the update works.
Reopen if you have a way to reproduce that.
With MonoDevelop 188.8.131.52, using the assembly browser to browse List<T>, or any of the MonoTouch types.
Notice how private members are being rendered, despite the setting:
It seems like the combobox merely affects whether types are shown or not, it does not affect the rendering of the decompiled text, which always shows the private members.