Rename IHttpContextAccessor.Value to IHttpContextAccessor.HttpContext

[muratg]

[HaoK]

@davidfowl filed aspnet/Options#31 to change Options.Options -> Value, HttpContextAccessor seems to be going the other direction, do we have final consensus for naming these properties (Value or Type name)?

cc @divega @yishaigalatzer

[yishaigalatzer]

I'm game for whatever of the two as long as its consistent

[Praburaj]

@davidfowl ?

[davidfowl]

I dunno the 2 things need to be consistent. Look at the usage patterns:

private FooOptions _options;
public Foo(IOptions<FooOptions> options)
{
  _options = options.Options;
}

VS

private IHttpContextAccessor _accessor;
public Foo(IHttpContextAccessor accessor)
{
    _accessor = accessor;
}

[HaoK]

But IOptions true name was/is IOptionsAccessor, so it feels like they really should have the same naming pattern