Razor runtime generates potentially conflicting using statements for TagHelper infrastructure.

[NTaylorMullen]

Today a Razor page will generate the following boiler plate infrastructure at runtime:

#pragma warning disable 0414
private TagHelperContent __tagHelperStringValueBuffer = null;
#pragma warning restore 0414
private TagHelperExecutionContext __tagHelperExecutionContext = null;
private TagHelperRunner __tagHelperRunner = null;
private TagHelperScopeManager __tagHelperScopeManager = new TagHelperScopeManager();

Which then requires the following two using statements:

using Microsoft.AspNet.Razor.TagHelpers;
using Microsoft.AspNet.Razor.Runtime.TagHelpers;

This can be troublesome when writing your Razor page's and then magically having them explode if you have a conflicting type in the page at runtime. We should transition the infrastructure pieces to use fully qualified names.

[Eilon]

You mean if they happen to have a type called TagHelperRunner? But yeah we should always code-gen global::Microsoft.AspNet.Foo.Bar.Quz no matter what.

[NTaylorMullen]

Yup 😄

[NTaylorMullen]

a76f16c
aspnet/Mvc@5ad1a27