IFeatureCollection indexer is pretty bad

[lodejard]

This usage is pretty awful:

var feature = httpContext.Features[typeof(IServiceProvidersFeature)] as IServiceProvidersFeature;

It doesn't show up in intellisense, and GetFeature/SetFeature don't appear on HttpContext...

Didn't we have something more like this at one point?

var feature = yadda.GetFeature<IServiceProvidersFeature>();

[Tratcher]

It moved to httpContext.Features.Get<T>();

[lodejard]

Oh, the namespace using Microsoft.AspNet.Http.Features; means it pretty much won't show up if you don't already know it exists. Is there anything we can do about that?

[Tratcher]

All the interfaces are also on that namespace, so you need to add it anyways. Would be nice if we could make the first time intellesence work better though.

VS feature? Consider the namespace of the thing currently being operated on?

[davidfowl]

We can't rely on VS features. We should move things around

[Tratcher]

Just keep in mind that Features are for advanced scenarios like middleware authoring, don't munge them in with all the beginners stuff.

[HaoK]

Just a +1, I was looking for these methods, and it was hard to find them even looking for them :)

I ended up needing all 3 namespaces for the IServiceProviders change:

using Microsoft.AspNet.Http;
using Microsoft.AspNet.Http.Features;
using Microsoft.AspNet.Http.Features.Internal;

[davidfowl]

Ugh

[muratg]

Collapsing namespaces is also a solution.

[Tratcher]

Resolved by #522