-
Notifications
You must be signed in to change notification settings - Fork 10.7k
Allow Core Razor editor to work in non-project scenarios. #5072
Copy link
Copy link
Closed
Labels
area-mvcIncludes: MVC, Actions and Controllers, Localization, CORS, most templatesIncludes: MVC, Actions and Controllers, Localization, CORS, most templatescost: LWill take from 5 - 10 days to completeWill take from 5 - 10 days to completeenhancementThis issue represents an ask for new feature or an enhancement to an existing oneThis issue represents an ask for new feature or an enhancement to an existing onefeature-razor-pages
Milestone
Metadata
Metadata
Assignees
Labels
area-mvcIncludes: MVC, Actions and Controllers, Localization, CORS, most templatesIncludes: MVC, Actions and Controllers, Localization, CORS, most templatescost: LWill take from 5 - 10 days to completeWill take from 5 - 10 days to completeenhancementThis issue represents an ask for new feature or an enhancement to an existing oneThis issue represents an ask for new feature or an enhancement to an existing onefeature-razor-pages
Type
Fields
Give feedbackNo fields configured for issues without a type.
Today if a Razor file is opened outside of the context of a project (diffing two Razor files) there is no IVsHierarchy and therefore no project path or any project information.
Our system relies on the idea that a document conceptually has a project; however, this is not true in the diff scenario and technically not true in the ctrl + o scenario for a Razor file (ctrl + o uses old Razor editor today).
This crashes VS.