Designer support for Razor pages
Razor based pages need a design surface in the same way as ASP.Net Forms pages or straight HTML. This should support dropping of controls onto the page, dragging of margins and padding, and all the other features we have normally in design view.
I agree that there should be a down vote button. How hard is it to click the save button and refresh the page? Design mode was always horrible. Get good at programming.
Nathan Smith commented
-3 Down Vote
-1M NO! stick to the code. where's the downvote button?
Kat Lim Ruiz commented
no, leave it as no design. ASPNET Web Forms designer was awful and created a lot of waste and garbage tagging (<Font>!).
What you can have is a previewer embedded in Visual Studio, but not a designer.
Siva Katir commented
While not fully what you're asking for you can use Browser Link (http://www.asp.net/visual-studio/overview/2013/using-browser-link) to change HTML and CSS from any browser's inspector.
I kind of hope that drop in controls never exist just because the HTML that they output has historically been worse then garbage. That said there are tools that do that such as DreamWeaver, but really, look at the code that it outputs. HTML isn't nearly as complex as say XAML to demand something like a WYSIWYG editor, IMHO.
Graham O'Riley commented
I agree with the comments so far. The reason companies changed to asp.net was for the web design like features. Hand coding asp pages wasn't pleasant and nor is mvc razor views. The page inspector is a little help but you can't alter the html from within it? Strange!!
Brian Baker commented
Definitely some version of expression web that is integrated with visual studio is necessary so there is a design surface for MVC razor views. The current method of hand coding, compiling and previewing is an insane waste of productivity (from a design point of view) and removes the designers from working directly on a finished product. Is MS wants people to make great products with their software they are going to have to incorporate the design community in a greater role.
Current implementation is very similar to the bad old days of Classic ASP; please change this