This is the first step on the journey to replacing RazorEditorParser. We can't just get rid of this because VS is using it today.