At the moment the DynamicItemHandler hardcodes the item type for Razor files which means there is no way to opt into the Razor editor lighting up, without also affecting build/publish/packaging. For large enterprise solutions (Bing, OrchardCore, etc.) where the Web SDK is not in use this means the Razor editor doesn't work correctly.

The Razor tooling team is wanting to enable this item type to come from a property that is read at evaluation so that in the project system design time targets this can be set to None and in the Web SDK (or possibly the Razor tooling targets) it can be set to Content to preserve the existing behaviour.

/cc @tmeschter @NTaylorMullen