Bug 4915 - HashSet has never offered popup help
Summary: HashSet has never offered popup help
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Project Model ()
Version: 2.9.x
Hardware: PC Windows
: High normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2012-05-07 01:10 UTC by John Costella
Modified: 2013-09-03 09:33 UTC (History)
2 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 John Costella 2012-05-07 01:10:00 UTC
(Not sure if this is text editor. Please amend if not.)

A minor issue, but it has always been perplexing to me that HashSet<T> never appears in any code completion list, and no helpful parameter lists etc. ever appear for it. (But it compiles fine.)

e.g. (by contrast) if you type

  var r = new Dic

then you get 'Dictionary<TKey, TValue>' as the middle of three suggestions, and once you get to

  var r = new Dictionary<int, int>(

you get a beige sidebox with 1 of 6 constructor variations. Very helpful.

But if you type

  var r = new Has

then you get a pink box with "No matches" in it, and you never get any help with HashSet parameters or methods at all.

This has been the case for a long time (years) and is still the case in 2.9.5 alpha.

By itself, close to trivial, but it's a weird one, which might have other consequences.
Comment 1 Mike Krüger 2012-05-07 01:56:12 UTC
It's because the project system doesn't give the (default) System.Core reference.

If you add System.Core to the references it should work.
Comment 2 John Costella 2012-05-07 02:04:26 UTC
Ah, fascinating. I didn't realise that System.Collections.Generic was split like this.

Is this a bug in the project system? I would have thought that either the reference should be needed to use HashSet<T> at all, or else if it is implicitly there for using it that it would be implicitly there for popup help too. (Not just being precious about popup help here: I want to make sure my projects have the correct references defined in them.)
Comment 3 Lluis Sanchez 2013-06-12 11:22:19 UTC
Mike, looks like the System.Core reference is implicit in VS. Can we do the same?
Comment 4 Mikayla Hutchinson [MSFT] 2013-06-17 20:31:39 UTC
It's not implicit in VS, it's an implicitly referenced assembly in the default MSBuild targets. So technically it should come from the non-MSBuild fallback of DotNetAssemblyProject.GetReferencedAssemblies IF targeting 3.5 or later...
Comment 5 Lluis Sanchez 2013-09-03 09:33:05 UTC
Although it is implicitly referenced in MSBuild, the ResolveAssemblyReferences target doesn't return it, so DotNetAssemblyProject has to return it in when using MSBuild too. Fixed in master.