Bug 5012 - Public only assembly browser should not show private namespaces
Summary: Public only assembly browser should not show private namespaces
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Assembly browser ()
Version: Trunk
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2012-05-10 17:02 UTC by Mikayla Hutchinson [MSFT]
Modified: 2012-07-26 18:00 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Mikayla Hutchinson [MSFT] 2012-05-10 17:02:54 UTC
When the assembly browser is in "public only" mode, it should not show namespaces that only contain internal/private classes.
Comment 1 Mike Krüger 2012-05-21 08:00:51 UTC
Comment 2 Peter Collins 2012-07-26 17:58:08 UTC
This bug seems to have resurfaced in MonoDevelop 3.0.4 on OS X Lion 10.7.4
(git build info for my MD version: 4d4277560e5f4e0758948f3ddf4180e876c9cadc-dirty)

Below is a screen shot of a private member being displayed while "Only public members" is selected.

Comment 3 Peter Collins 2012-07-26 18:00:35 UTC
I reopened this by mistake, I was actually thinking about protected methods not private. This bug still seems to be fixed.